Skip to Content
avatar image
Former Member

scenario

Can anybody tell me any scenario with business requirement how to start it and end it.(without links)

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

5 Answers

  • avatar image
    Former Member
    Aug 31, 2008 at 09:09 AM

    Hi,

    Any XI/PI scenario starts with basic information as follows

    A] Get basic Details of Sender and receiver systems.

    Get details about sender system and receiver systems. for e.g. SAP r/3, File, Web application etc.

    B] Design the scenario as per the requirments

    Get the sender/receiver data format and create the data types, message types, message interface etc.,

    Do the mapping and interface mapping

    C] Configure the ID part

    Configure the Sender and receiver system, like Receiver determination, interface determination, sender/receiver agreements etc,

    D] Check with the Communication channels and Firewall securities across the B2B or A2A scenarios if any

    E] Deploy & Monitor the interface

    Basically these are the steps followed along with proper documentation of each step.

    Thanks

    swarup

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 01, 2008 at 08:55 AM

    XI Implementation Methodology Worksheet

    Summary

    The goal of this document is to provide a guide to the methodology steps that make up an XI implementation. The customer can use this worksheet to gather all necessary information to prepare for the implementation.

    Methodology Steps

    The steps (1) through (4) can be viewed as prerequisites. They can be completed before the XI system is even installed onsite. This will greatly reduce the implementation time. Typically these are also the most time-consuming steps of the project. Multiple tasks can be done in parallel. This should be reflected in the project plan.

    1. Scenario Analysis

    Description of the business scenario to be implemented.

    What types of backend systems are involved (mainframe, SAP, etc.)?

    Is this a new development or a replacement for an existing interface?

    Deliverables

    High-level scenario description.

    Description of existing scenario implementation, if applicable.

    Description of XI-based scenario.

    Resources

    Technical architect

    Functional architect

    XI product expert

    Corresponding XI Activities

    Create entries in System Landscape Directory, as appropriate.

    2. Interface Analysis

    Is the interface synchronous or asynchronous?

    Does the interface require a technical or application acknowledgement?

    For each interface, identify the outbound and inbound messages.

    Determine data structures for each message type, as applicable.

    Determine flat file format or database structure.

    Determine IDoc / RFC / BAPI structure.

    Determine XML data structures.

    Provide data samples for each message type.

    Deliverables

    Inbound/outbound message structure definition

    Data samples for each message

    Resources

    Technical and functional analysts for each system to be connected

    Corresponding XI Activities

    Create interface objects in Integration Repository.

    3. Mapping Definition

    Based on deliverables from Step 2, identify mapping rules between each pair of interfaces. This activity typically requires the involvement of business analysts who have knowledge of the business semantics of each interface.

    Deliverables

    Mapping specification including source fields, target fields, and transformation rules. Typically this is delivered in the form of a spreadsheet.

    Resources

    Functional analysts for each system to be connected

    Corresponding XI Activities

    Choose implementation technology for mappings (graphical tool, XSLT, Java).

    Implement mapping based on business rules defined in Step 3 and interface samples and metadata defined in Step 2.

    4. Preparation of the Environment

    A test environment must be defined. If B2B integration (across the firewall) is involved, then network connectivity issues need to be addressed. This may include the configuration of proxies, reverse proxies, or other devices located in the DMZ.

    Preparation of the test environment includes, of course, the installation and basic post-installation steps of the XI system.

    If the scenario is to become productive, then a promote-to-production strategy must be defined and the XI environment must be replicated accordingly (i.e., DEV, QA, PRD).

    Deliverables

    XI system is installed.

    Test environment is ready.

    Network connectivity is established between XI and all participating systems.

    5. Configuration

    There are two parts to the configuration step: backend system configuration and XI configuration.

    Prepare backend applications for message exchange. The backend systems need to be configured to send and receive messages to/from XI. This configuration must be such that the application can produce or receive data samples such as the ones delivered in Step 2.

    Based on deliverables from Steps 1, 2, 3, configure XI objects in Integration Directory.

    Deliverables

    Backend systems are ready to produce and consume messages as defined in XI scenario.

    XI system (Integration Directory) is configured.

    Resources

    Technical specialists for each system to be connected

    XI specialist

    6. Testing

    The end-to-end scenario can be tested with different data sets. The testing environment has been prepared beforehand and network connectivity issues have been resolved.

    Deliverables

    Sign off on scenario.

    Resources

    Technical and functional analysts

    XI specialist

    "Award points if helpful"

    Regards,

    Jayasimha Jangam

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 01, 2008 at 09:04 AM

    Hi ,

    Bussiness requirement depends on the landscape and scope defined.Requirement of an Integration Scenario thru XI is purely depend on the decision taken to go with XI/PI..

    Once the decision is made, Scope is defined in terms of how many systems are there to integrate etc.. You need to understand the both souce and target systems how they handle data, what is the protocol, format, security concerns ,compatibility etc.. Based on this you can define the requirement saying that, form System A to System B it should be File to IDOC or any...

    Understanding the both systems and requirement of scope will lead to identify the type of scenarios..

    For instance let us take few examples:

    1. FILE TO IDOC.

    When u have ur master data stored in a file thru a legacy system say in some xml format then u may need to have this scenario configured.

    2. FILE TO RFC.

    Consider pt1 but here for example consider delete scenario. when u have deleted the mater/transaction u may need to update another file...so in this case u will need to config this scenario...y we cannot use idoc is becoz sync scneario is not possible with idoc but yes with rfc

    3. FILE TO JDBC scenarios?

    u have some business data extracted from a file and before u update a r3 transaction u may need to refer a datbase table to read some data baed on keyfield...so u will take a jdbc response and based on that u may validate with the data for r3 updation.

    the scenario keeps varying in real life and the above are very few examples of the kind of scenario that would exists in the business world.

    Bussiness requirement depends on the landscape and scope defined.Requirement of an Integration Scenario thru XI is purely depend on the decision taken to go with XI/PI..

    Once the decision is made, Scope is defined in terms of how many systems are there to integrate etc.. You need to understand the both souce and target systems how they handle data, what is the protocol, format, security concerns ,compatibility etc.. Based on this you can define the requirement saying that, form System A to System B it should be File to IDOC or any...

    Understanding the both systems and requirement of scope will lead to identify the type of scenarios..

    Regards,

    Vinod.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 01, 2008 at 09:12 AM

    Hi P k.,

    I just elaborate u more practicalyy,

    first u need to define the source i,e sending structure for that u need to know from where the file is coming is the file is in understandable format of XI if not which adapter is to be used to make the content understandable to XI .. then u will be designing the structure..

    Then u need to analyse where this data to be sent, is it an SAP or legacy system depending on that choose the adpater to delver the content to the target.. by defining its target structure..

    So, For designing u will go to Integration Repository ..

    Interface Object ---> Data Types -- Where the structure of the source or target will be defined

    As the message interface doesn't realise this datatypes it requires message types as an input we will be assigning this datatypes to Messagetypes where this message types is tagged to Message Interfaces

    Interface Object --- Message Interfaces (3)

    -


    Message Types (2)

    --- Data Types -- (1)Struuctures defined

    Then develop the message mapping by retrieving its source and target structure and develop the message mapping and test it there using TEST tab..if every thing is fine then go to INTERFACE MAPPING..

    Mapping Objects ---> Interface Mapping (5)

    -


    Message Mapping (4)

    as per the above numbering create the objects and activate it.. using changelist option..

    then go to Integration directory..

    with respect to the sender and receiver systems choose the business system/service.. then configure the communication channels under the business system/service w.r.t the structures u defined choose the adapters in the communication channels..

    Configure the adapters and then create Sender/Receiver aggrements, Receiver Determination and Interface determination by giving the essential crendentials..

    We have differing ways to monitor whether the message is delivred or not..

    1. Go to SXMB_MONI and check the flag about the status of the message..

    2. Goto RWB in Browser and there we can monitor through coomunication channel monitoring available in Component Monitoring or using Message monitoring also we can trace if any errors.

    post if any queries..

    regards,

    Kishore

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 01, 2008 at 09:15 AM

    Hi,

    Get the complete details about the system landscape

    Define the sender and the receiver systems

    Gather the necessary technical & business system information.

    Define the different types of interfaces involved in the the process.

    For ex: file to file, file to JDBC, file to RFC, IDocs etc.

    Check what type of requirement you have and in case of RFC' or idocs choose the IDocs or RFCs which suits ur requirement.

    Start defining the source and the target structure.

    Do necessary mapping, configure the communication channel and adapter etc along with the agreements and determincation.

    then test the scenario and start monitoring.

    Regards,

    Nithiyanandam

    Edited by: Nithiyanandam A.U. on Sep 1, 2008 11:18 AM

    Add comment
    10|10000 characters needed characters exceeded