Explore topic-wise InterviewSolutions in .

ORACLE and MS SQL

oracle and ms sql

MESSAGE monitoring, COMPONENT monitoring, performance analysis and message alerting.

message monitoring, component monitoring, performance analysis and message alerting.

ENABLES partners of XI CUSTOMERS to CONDUCT XML document EXCHANGE with XI.

enables partners of XI customers to conduct XML document exchange with XI.

INTEGRATION ENGINE.

integration engine.

CCMS (computer center management SYSTEM), pmi (process monitoring INFRASTRUCTURE) and alert frame WORK.

ccms (computer center management system), pmi (process monitoring infrastructure) and alert frame work.

ALRTCATDEF.

ALRTCATDEF.

they have sapmuser roles on the abap PART of the SAP web as that is AVAILABLE on the J2ee part as GROUPS.

they have sapmuser roles on the abap part of the SAP web as that is available on the J2ee part as groups.

EXACTLY once and exactly once in ORDER.

exactly once and exactly once in order.

Receiver determination rules and INTERFACE determination rules (INCLUDES MAPPING ASSIGN).

Receiver determination rules and interface determination rules (includes mapping assign).

inbound handling, receiver DETERMINATION, interface determination, CHANNEL determination, mapping, OUTBOUND handling.

inbound handling, receiver determination, interface determination, channel determination, mapping, outbound handling.

mobile INFRASTRUCTURE, enterprise PORTALS, biw and MDM, sap xi (integration BROKER and bpm) WEB AS.

mobile infrastructure, enterprise portals, biw and MDM, sap xi (integration broker and bpm) WEB AS.

PEOPLE INTEGRATION, INFORMATION integration, process integration and application PLATFORM.

People integration, information integration, process integration and application platform.

SAP NetWeaver provides an open integration and application platform and PERMITS the integration of the Enterprise Services Architecture. NET weaver covers following topics:

1. PEOPLE Integration
2. Process Integration
3. INFORMATION Integration
4. Application Platform.

SAP NetWeaver provides an open integration and application platform and permits the integration of the Enterprise Services Architecture. Net weaver covers following topics:

USE the TRANSACTION CODE SXMB_MONI_BPE.

Use the transaction code SXMB_MONI_BPE.

This error occurs in CASE of scenarios with IDOC ADAPTERS. Whenever you use BUSINESS SYSTEMS, make sure that the corresponding logical system name is maintained in the SLD.

Open your business system in the Integration Directory. Switch to Change mode. Access the MENU path Service → Adapter Specific Identifiers. Click the button that says 'Compare with System Landscape Directory' and chose Apply. Save and activate your change list.

In case of business services, you can manually type a logical system name in the Adapter Specific Identifiers if required. This name should match the corresponding logical system name defined in the partner SAP system's partner profiles.

This error occurs in case of scenarios with IDOC adapters. Whenever you use business systems, make sure that the corresponding logical system name is maintained in the SLD.

Open your business system in the Integration Directory. Switch to Change mode. Access the menu path Service → Adapter Specific Identifiers. Click the button that says 'Compare with System Landscape Directory' and chose Apply. Save and activate your change list.

In case of business services, you can manually type a logical system name in the Adapter Specific Identifiers if required. This name should match the corresponding logical system name defined in the partner SAP system's partner profiles.

CHECK the queues using TRANSACTIONS SMQ1 (outbound)/SMQ2 (inbound). RESOLVE the displayed errors. You can cancel the messages from SXMB_MONI. EXECUTE LUW if necessary and avoid deleting entries manually.

Check the queues using transactions SMQ1 (outbound)/SMQ2 (inbound). Resolve the displayed errors. You can cancel the messages from SXMB_MONI. Execute LUW if necessary and avoid deleting entries manually.

Go to transaction IDX2 --> DELETE the OLD IDOC structure and LOAD the new IDOC structure

Go to transaction IDX2 --> Delete the old IDOC structure and Load the new IDOC structure

You can test the ALERT by EXECUTING the report RSALERTTEST.

To check the log, EXECUTE the report SXMSALERT_LOGREADER.

You can test the alert by executing the report RSALERTTEST.

To check the log, execute the report SXMSALERT_LOGREADER.

Create a workbench transport request manually with transaction SE09. Delete the corresponding unclassified task of that request. Double click on the transport request and click on button 'edit <-> change'. For Program ID ENTER R3TR, for Object Type enter TABU and for Object NAME enter SXMSALERTRULES.

Now click on the button with the key symbol (located under 'Function'). Click on 'Insert ROW' and enter * for table key. Save the request, release it and import it in the target system. Refer SAP Note 1110295

Create a workbench transport request manually with transaction SE09. Delete the corresponding unclassified task of that request. Double click on the transport request and click on button 'edit <-> change'. For Program ID enter R3TR, for Object Type enter TABU and for Object Name enter SXMSALERTRULES.

Now click on the button with the key symbol (located under 'Function'). Click on 'Insert row' and enter * for table key. Save the request, release it and import it in the target system. Refer SAP Note 1110295

Go to IR -> Menu -> ENVIRONMENT --> Clear SLD DATA CACHE

Go to ID -> Menu -> Environment --> Clear SLD Data Cache

Go to IR -> Menu -> Environment --> Clear SLD Data Cache

Go to ID -> Menu -> Environment --> Clear SLD Data Cache

Go to TRANSACTION SE01 -&GT; TRANSPORTS -> Global Information -> Transports -> check the error displayed there.

Also confirm that the business SYSTEMS are ready for source and target system before transportation.

Go to transaction SE01 -> Transports -> Global Information -> Transports -> check the error displayed there.

Also confirm that the business systems are ready for source and target system before transportation.

The problem is in CACHE refresh.

GO to SXI_CACHE, then from Menu - XI RUNTIME Cache - choose "Start Delta Cache Refresh" (F6) and then choose "Start Complete Cache Refresh" (shift + F6)

The problem is in Cache refresh.

Go to SXI_CACHE, then from Menu - XI Runtime Cache - choose "Start Delta Cache Refresh" (F6) and then choose "Start Complete Cache Refresh" (shift + F6)

The problem is that the file is not able to GET any party or SERVICE CONFIGURED for itself.

Check the structure of input file and CONFIRM that the same structure is assigned to Sender Interface.

The problem is that the file is not able to get any party or service configured for itself.

Check the structure of input file and confirm that the same structure is assigned to Sender Interface.

PROBLEM is in Receiver Determination. Check it. If everything is fine then just edit and change SOMETHING then remove that change and again REACTIVATE the receiver determination.

Problem is in Receiver Determination. Check it. If everything is fine then just edit and change something then remove that change and again reactivate the receiver determination.

The file got STUCKED in the PI queue. Check the following.

1. qRFC MONITORING: transaction SM58 Click DEREGISTRATION Click Registration
2. qRFC MONITOR (OUTBOUND queue) Check the queue and monitor the problem
3. qRFC monitor (Inbound queue) Check the queue and monitor the problem

The file got stucked in the PI queue. Check the following.

The error is in Message Mapping. Check the node XXX and MAKE sure all its attributes are mapped properly. For EX: SEGMENT="1" and BEGIN="1"

The error is in Message Mapping. Check the node xxx and make sure all its attributes are mapped properly. For Ex: SEGMENT="1" and BEGIN="1"

1. The error is in Message Mapping. Go to the Test tab and test the message mapping with the incoming payload FILE.
2. Check the source structure with the input file that you are sending to XI. Both STRUCTURES should be exactly same. I mean all nodes and the node structures.
3. Refresh the cache (both Delta cache and FULL cache) in SXI_CACHE transaction in PI.

Go to transaction SICF /default_host/sap/xi/engine double CLICK on service Now check whether you have ENTERED CORRECT information for the following FIELDS. Client, user id, password, and language information.

Go to transaction SICF /default_host/sap/xi/engine double click on service Now check whether you have entered correct information for the following fields. Client, user id, password, and language information.

It DEPENDS on the CLIENT REQUIREMENT.

It depends on the client requirement.

It depends on the CLIENT requirement but you should know about the R3-MDM integration.most of the requirement it would be use. Related SCENARIOS as I MENTIONED are MDM-BIW integration, SRM-MDM Catalog, MDM-XI-R3 integration, RPCM,ENRICHMENT adaptor ETC...

It depends on the client requirement but you should know about the R3-MDM integration.most of the requirement it would be use. Related scenarios as I mentioned are MDM-BIW integration, SRM-MDM Catalog, MDM-XI-R3 integration, RPCM,enrichment adaptor etc...

A Communication party represent a LAYER unit which is involved in cross-system process (EG. a company). and Business service represent an abstract, addressable unit. business services are USED in cross-company process. for eg if the parties involved have only published there interfaces and not there system landscape or it is partly known. NORMALLY we use business services to communicate with different systems in same company.

A Communication party represent a layer unit which is involved in cross-system process (eg. a company). and Business service represent an abstract, addressable unit. business services are used in cross-company process. for eg if the parties involved have only published there interfaces and not there system landscape or it is partly known. normally we use business services to communicate with different systems in same company.

YES, RFC ADAPTER can be USED for asynchronous PROCESSING.

YES, RFC adapter can be used for asynchronous processing.

Yes

Yes

SELECT, INSERT, DELETE, UPDATE.

SELECT, INSERT, DELETE, UPDATE.

JDBC ADAPTER CONVERTS database content to XML messages and the other WAY around.

JDBC adapter converts database content to XML messages and the other way around.

MESSAGING SYSTEMS to the INTEGRATION ENGINE

Messaging systems to the integration engine

PRODUCT: REPRESENTS a collection of all versions of a product. In SAP environment, a product corresponds to an SAP TECHNICAL Component, e.g. 4.6c, 4.6d, and 4.7 COMPONENT: Represents a collection of all versions of a SOFTWARE COMPONENTS Examples of Software components are SAP_APPL, SAP_ABA, SAP_HR Software.

PRODUCT: Represents a collection of all versions of a product. In SAP environment, a product corresponds to an SAP technical Component, e.g. 4.6c, 4.6d, and 4.7 COMPONENT: Represents a collection of all versions of a software components Examples of Software components are SAP_APPL, SAP_ABA, SAP_HR Software.

MESSAGE TYPE

MESSAGE TYPE

ExchangeFaultdata and EXCHANGE LOG DATA.

ExchangeFaultdata and Exchange log data.

BUSINESS SYSTEM WIZARD

Business system wizard

If you have been interacting with the client for gathering the REQ need to explain them on what basis the req were gathered.

These are the things you can ask the client to get the requirements:

1. What is the problem? This will give answer for why they are going for XI? Here try to Understand the business as well as integration? Where XI come into the picture?
2. Total number of systems involved in integration? That is their SLD? Details?
3. Scenarios (interfaces)? Total? What kind of? But here once again this is depends on project. Some TIMES client will give this (or) based on the requirement you people have to decide? It is fully depends..!!!! take care
4. Then based on the scenario you need to get the full information ....this is place where you can ask all the QUESTIONS from scenario to scenario. Get all the details as mentioned below apart from the basics try to ask something technically.
5. Are they providing any XSD,WSDL, documents, Naming conventions..etc
6. Protocols related like http, ftp, smtp, soap....
7. If file related then CSV, Fixed....like that delimiter specific details.very IMP this one.
8. If R/3 present then ....it is Idoc, Rfc, BAPI,....any proxies and web SERVICES for direct communication ....etc

These are the basic things for XI integration project and after that every thing is specific to scenarios.

If you have been interacting with the client for gathering the req need to explain them on what basis the req were gathered.

These are the things you can ask the client to get the requirements:

These are the basic things for XI integration project and after that every thing is specific to scenarios.

Monitoring after golive. troubleshoot performance issue when a TICKET arises. on development part it will be creating BS, OBJECTS in IR, configuring in ID Based on the SCENARIO that what you are working in the low level Working on SLD,IR,ID,RWB + developing the scenario+Documentation + Based on the requirements design + monitoring CHECK + Performance+..etc

Monitoring after golive. troubleshoot performance issue when a ticket arises. on development part it will be creating BS, objects in IR, configuring in ID Based on the scenario that what you are working in the low level Working on SLD,IR,ID,RWB + developing the scenario+Documentation + Based on the requirements design + monitoring check + Performance+..etc

USUALLY we will use Development SYSTEM, TESTING System(QA), Production System. But some times we will use Pre-Prod (Pre Production System) also. Before you moving all INTERFACES to Production will use Pre-Prod to test all interfaces with huge volumes. So totally will use following systems for an implementation:

DEV
QA
Pre-Prod
Prod

Usually we will use Development System, Testing System(QA), Production System. But some times we will use Pre-Prod (Pre Production System) also. Before you moving all interfaces to Production will use Pre-Prod to test all interfaces with huge volumes. So totally will use following systems for an implementation:

DEV
QA
Pre-Prod
Prod

It is an alert and monitoring for the ERROR MESSAGES. To monitor SAP components . CCMS is SAP Computing Center Management System. RWB is smoothly integrated with CCMS and CCMS alerts can be viewed thro' the Runtime WorkBench. It provides alert monitoring for SAP EXCHANGE Infrastructure Which is used for monitoring any system ERRORS and administration errors. Enables monitor entire system centrally.

It is an alert and monitoring for the error messages. To monitor SAP components . CCMS is SAP Computing Center Management System. RWB is smoothly integrated with CCMS and CCMS alerts can be viewed thro' the Runtime WorkBench. It provides alert monitoring for SAP Exchange Infrastructure Which is used for monitoring any system errors and administration errors. Enables monitor entire system centrally.

SAP NetWeaver XI integration where the Involvement of charing the information between SAP and Non SAP SYSTEM comes into PICTURE.

Implementation where the SAP involvement into the business coming into Picture.

GO Alive After Developing the interface after come acrossing various stages like testing the Interface is made alive or used to the real TIME scenario is said to be GO ALIVE.

SAP NetWeaver XI integration where the Involvement of charing the information between SAP and Non SAP System comes into Picture.

Implementation where the SAP involvement into the business coming into Picture.

Go Alive After Developing the interface after come acrossing various stages like testing the Interface is made alive or used to the real time scenario is said to be GO ALIVE.

SAP GIVES US following options to communicate with SAP systems.

1. IDoc ADAPTER
2. RFC Adapter
3. PROXY

SAP gives us following options to communicate with SAP systems.

MAINTAIN the Idoc Metadata. This is needed only by XI, and not by other SAP SYSTEMS. IDX2 is needed because XI needs to CONSTRUCT IDoc-XML from the IDoc. No other SAP system needs to do that.

Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.

YES, it is POSSIBLE.

Yes, it is possible.

Container object---> can be only used in the function it is DEFINED in.

Global container----> it can be used and remain visible ACROSS the different function.

Global container---> in the old days it was used to store objects in mappings now we can use global variables instead.

Container Object: This object enables you to CACHE the values that you want to read again when you next call the same user-defined function.

From SP14 and above avoid Global Container. Use Java Section of Message Mapping to DEFINE Global Variables and to use them in your UDF's.

Container object---> can be only used in the function it is defined in.

Global container----> it can be used and remain visible across the different function.

Global container---> in the old days it was used to store objects in mappings now we can use global variables instead.

Container Object: This object enables you to cache the values that you want to read again when you next call the same user-defined function.

From SP14 and above avoid Global Container. Use Java Section of Message Mapping to define Global Variables and to use them in your UDF's.

Both RFC and IDOC ADAPTER you can use for connecting SAP ECC from PI. But IDOC adapter you can use only for Asynchronous COMMUNICATION while RFC adapter you can use for Synchronous ALSO.

Both RFC and IDOC adapter you can use for connecting SAP ECC from PI. But IDOC adapter you can use only for Asynchronous communication while RFC adapter you can use for Synchronous also.