Step by Step XI practical scenarios

Hi!
I have first practical experience working with SAP XI 7.0 and searching for practical Step by Step scenarios:
- IDOC to IDOC scenarios
- ABAP or Java Proxy scenarios
- scenarios with SOAP adapter
Has some one seen in SDN-blog or in other sources such documentation or can share his/her own examples?
Any helpful information will be very appreciated.
Thank you very much!
regards
Holger

Hi Thomson,
Just Search in SDN you will get almost all scenarios.
Following are the links to weblogs which will help to develop the basic scenarios.
Introduction to IDoc-XI-File scenario and complete walk through for starters. - IDoc to File
ABAP Proxies in XI(Client Proxy) - ABAP Proxy to File
FILE to JDBC Adapter using SAP XI 3.0 - File to JDBC
File to R/3 via ABAP Proxy - File to ABAP Proxy
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1) - File to File Part 1
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2) - File to File Part 2
Convert any flat file to any Idoc-Java Mapping - Any flat file to any Idoc
RFC Scenario using BPM --Starter Kit - File to RFC
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1685 [original link is broken] [original link is broken] [original link is broken] - File to Mail
Dynamic File Name using XI 3.0 SP12 Part - I - Dynamic File Name Part 1
Dynamic file name(XSLT Mapping with Java Enhancement) using XI 3.0 SP12 Part -II - Dynamic File Name Part 2
The specified item was not found. - Dynamic Mail Address
Understanding message flow in XI - Message Flow in XI
Walkthrough with BPM - Walk through BPM
Schedule Your BPM - Schedule BPM
Demonstrating Use of Synchronous-Asynchronous Bridge to Integrate Synchronous and Asynchronous systems using ccBPM in SAP Xi - Use of Synch - Asynch bridge in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] - Use of Synch - Asynch bridge in ccBPM
The specified item was not found. - Maintain RFC destination centrally
Triggering e-Mails to Shared folders of SAP IS-U - Triggering Email from folder
Outbound Idoc's - Work around using "Party"? - Handling different partners for IDoc
/people/siva.maranani/blog/2005/08/27/modeling-integration-scenario146s-in-xi - Modeling Integration Scenario in XI
The specified item was not found. - Testing of integration process
The specified item was not found. - Authorization in XI
http://help.sap.com/saphelp_nw04/helpdata/en/58/d22940cbf2195de10000000a1550b0/content.htm - Authorization in XI
The specified item was not found. - Alert Configuration
The specified item was not found. - Trouble shoot alert config
Executing Unix shell script using Operating System Command in XI - Call UNIX Shell Script
Overview of Transition from Dev to QA in XI - Transport in XI
Using ABAP XSLT Extensions for XI Mapping - Using ABAP XSLT Extensions for XI Mapping
/people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure - Mail Adaptor options
IDOCs (Multiple Types) Collection in BPM - Collection of IDoc to Single File
XI : Controlling access to Sensitive Interfaces - Controlling access to Sensitive Interfaces
The specified item was not found. - The same filename from a sender to a receiver file adapter - SP14
Payload Based Message Search in XI30 using Trex Engine - Payload Based Message Search in XI30 using Trex Engine XI : Configuring CCMS Monitoring for XI- Part I - XI : Configuring CCMS Monitoring for XI- Part I
The specified item was not found. - XI: HTML e-mails from the receiver mail adapter
XI : FAQ's Provided by SAP (Updated) - XI : FAQ's Provided by SAP
Good Luck.
Regards,
Ramesh.

Similar Messages

Transformation step in ccBPM scenario

Hi There,
I have a scenario like this:
File -> ccBPM -> BAPI
I am using the Transformation step(1:1) in the ccBPM Scenario. I have supplied, interface mapping, source message (File name), target message (name) in the properties of the 'Transformation step'.
The scenario is currently failing at the Transformation step with a error message,"Expression must return the interface type Z_MYBAPI"
Any thoughts on this issue?
Thanks,
Raghu

Hi Raghu,
Check these:
1) Interface Mapping (shoould be between Abstract Interface).
2) Source Message and Target Message in transformation should be Abstract.
Hope these will help you.
Regards
Suraj

Need some practical Scenarios to test Compliance Calibrator, FF and AE

Hi Experts,
I have installed Compliance Calibrator 5.2 / Access Enforcer and Firefighter on a test System. However i am looking for some practical scenarios / Examples to test the functionlity of these installations. If any of you is currently working on these technologies i appreciate if you c an provide 2 3 scenarios to test my installation and functionality .
Thanks in advance.
Your help is much apprecaited..
SK

Hi SK,
Testing the functionality of CC
1. I would recommend to create some test roles where in you plug in some conflicting tcodes
    which can pose a sure SoD Risk, lets say Create Vendor Invoice(FB01) and Make an
    Automatic Payment(F110).
2. Now run the Risk Analysis by choosing the Default SAP GRC ruleset library and do a
    Role level Analysis.Then Assign the Test Roles to Test Users and then do a User Level Analysis.
3. You may have create some Custom Rule sets with appropriate naming of Conflicting functions
    like Creation of Purchase Order (P001), Approve Purchase Order(P002)
    in different Application Areas like Purchase 2 Pay(P2P), Order 2 Cash (O2D) and try to do
    the same as above two steps.
4. Test the functionality of Risk Remediation by removing the conflicting tcodes and do the
    Risk Analysis.Your previous Risk Roles must not appear
5. Test the functionality of Risk Mitigation by placing a mitigation Control on the Conflicting tcodes
   and do the Risk Analysis.Your previous Risk Roles must not appear if you have properly
    configured your CC
Testing the functionality of FF
1. I would say create a few Firefighter IDs in different functional areas like FI, SD, MM, and then
   create some test users for Firefighter Owners, Controllers and Firefighters who can use
   the functionality of FF.
2. Create some FF roles which have exceptional access in those functional areas
    encompassing transaction codes and authorization objects that are not used in normal incidents.
3. Assign each of the FF roles to the respective FF IDs and then to the test Firefighters.
4. Pull the log reports in FF and see if it gives exact details of the FF usage.
5. You may have take some assistance of the Functional team members to do the testing.
Testing the functionality of AE
1. Create a workflow scenario of hiring a new user.
2. Create the request under a test requestor. Assign the request to some test approver
3. Also Assign some roles and test the functionality.
Hope this helps for a good start
Regards,
Kiran Kandepalli.

Practical scenario.

hello,
Can anyone help me with giving a hint regarding practical scenario reports.
so that i can practise.
Thanks a lot in advance.
arpitha
[email protected]

Hi Arpita
Welcome to SDN!
I am giving you the Link from help.sap.com on BI content .
http://help.sap.com/saphelp_nw04/helpdata/en/29/79eb3cad744026e10000000a11405a/frameset.htm
This is for Supply chain Management and there are lot of practical reports (BI content Queries )
Install these Queries and ODS/Info cubes involved in the design . Load the data and execute these reports.
Happy Learning .
hope this helps
Regards
Pradip
(friends: don't forget to assign points to helpful answers )

How to connect steps in business scenario

Hello,
After creating a project in Solution Manager, creating a business scenario in that project and creating a custom business process in my scenario, Iu2019ve defined the necessary steps that I want in my process. These steps involve 2 different logical components, a component specified for a SAP XI/PI system and a logical component for SAP ECC system.
The business process will involve interaction between the two logical components where Idocs will be exchanged. My first issue is, in transaction SOLAR01 when I click the tab Graphic, Iu2019m able to see the two separate components each with their steps but with no connection or relation between them or with any step order. Where can I define the order and flow for the steps in the business process? After defining the flow, will the connections be presented in the graphic?
One other question, if this business process involve interfaces, should I define this as a business scenario or as an Interface Scenario? What is the main difference between these two objects? Canu2019t I have only business scenarios and define the steps as interfaces?
Thank your for the attention.
Best regards,
Goncalo Mouro Vaz

Hello,
please be aware that only business process maintained in the operations part of SAP Solution Manager. i.e. the Solution Directory, are available for Business Process Monitoring. Processes defined within SOLAR01 are in the project part and hence not directly available for monitoring. But those processes can be copied into the Solution Directory.
For BPMon only "Business Scenraios" are of interest. "Interface Scenarios" need not be maintained but can be used for additional documentation purposes.
Please refer to http://service.sap.com/bpm > Media Library > Technical Information > Setup for Interface Monitoring.pdf
You may also visit the FAQ page http://wiki.sdn.sap.com/wiki/display/SM/FAQBusinessProcess+Monitoring
Best Regards
Volker

Fork Step in BPM scenario PI 7.1

Hi All,
I have a requirement where in i will have to collect 3 different messages coming from the source and then combine these 3 messages to a single message and sent it to Target System .
To achieve this i came up with a BPM where in fork step was used and inside the fork step i added 3 branches with 3 receive steps to receive 3 different messages from the source .
Problem i am facing here is , the source system might send all the 3 messages or it might send only 2 messages or 1 message as well depening on the scenario .
So when we get only 2 messages frm the source system , fork step goes into waiting state since its waiting for the 3rd message also to come in . In this case i want the BPM to go ahead with 2 messages after a certain specified time (say 2 min) .
I tried adding wait step, deadline branch . Nothing seems to be working .
Please suggest what needs to be done here .
Waiting for your inputs
Regards
Vinay P.

Set Necessary Branches to 1 in the Fork properties. Use the fork inside a block with time out. In timeout branch throw an exception. Define an exception branch for that exception. It should work..!!
VJ

Where to chk the PipeLine process steps in BPM Scenario...

hi experts,
i hav a scenario where i need to send multile file formats to an synchronous R/3 system and from R/3 it needs to be forwarded to the Target system in file format... its a BPM scenario...
i need to CHK the sequence of Steps or Pipeline process to knw where exaclty the message is at each piont of time...
can any one help on this plz...
Thanks and Regards,
Srinivas

its possible to do the same using the ALERT Framework also...for the same pls go through the info provided below.
From SP 14 on PMI-free alerting was introduced. That means before SP 14 one has to configure and activate the End-to-End Monitoring, and to schedule the report SXMSALERT_PROCESS_DATA_GET in order to extract the alerts from the PMI data. For SP 14 and higher, that's not longer necessary.
If no alerts are being delivered, please check if "Suppress multiple alerts of this rule" is checked for your rule.
For SP 14 and higher you could also have a look at the report sxmsalert_logreader. This report shows some information about alerts being created or not.
You'll find more information about trouble shooting the alerting in SAP Note 913858.
Also just check if this batch program (RSALERTPROC) is running or not.
The links below on Alert Management (ALM) will be of good help to you:
http://help.sap.com/saphelp_nw04/helpdata/en/3f/567ddea69d3d4c93a6aedabd08899e/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/3f/81023cfa699508e10000000a11402f/frameset.htm
Also go through these blogs:
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1382. [original link is broken] [original link is broken] [original link is broken]
The specified item was not found.
The specified item was not found.
Meanwhile look at these forum threads also:
Alerts not getting triggered from Adapter Framework
Alert Configs...
Also, In ALRTCATDEF, go to SETTINGS--> CONFIGURATION. By default, the option selected is INTERNAL PROCESSING. Select the option SMTP FORWARDING AS XML and give the email id. This will enable you to send an email alert whenever an error occurs in XI.
I hope it helps you in finding a solution to your problem.

Receiver Determination steps for BPM scenario

Hi Experts,
Scenario : SOAP -> Calling different webservices
1. SOAP Client Request
2. Call the Initial webserive to get the unique Id. No need to pass any request to call this webservice, but it will give the response.
3. Take the Initial websrevice's response as a request to second webservice
4. Pass the SOAP client request to Third webservice
BPM steps
1. Receive Step for SOAP Request
2. Send Step for the Initial webservice call.
3. Transformation step Initial webservice response to request change.
4. Send Step for Second webservice (Pass the the Transformation step's target interface as a request)
5. Send Step for Third webservice ( Pass SOAP client request)
I am done with the BPM flow. Could you please help to do the Receiver Determination steps.
Usually I follow the below steps.
1. Sender Service to BPM
2. BPM to other services. I have a doubt with the second step. I am not passing the SOAP client request to Initial webservice. So, please tell me how to proceed further for the BPM Receiver Determination steps..
Thanks & Regards
Sara

Hey,
First, what is th purpose of your SOAP client request.
Is it just to trigger the BPM.
Second on what basis are you fetching the unique Id from initial web service.
If it is a normal scenario then, the reciever determination will be like this.
Soap client-> BPM
BPM->initial webservice
BPM->second webservice
BPM->third webservice
but in this particular scenario i dont know which data is being used to fetch the unique Id.
regards,
Milan

Reg:Steps in IDOC Scenario

Hi,
    I am very new to IDOC concept so can anyone tell me what is the use and why do we want to create,
1)RFC Destination
2)Port
3)Logical sysytem name
4)Partner Profile ,in IDOC Scenario and also let me know the steps that I have to implement while doing that scenario.
Thanks in advance
B.Lavanya

Hi,
This is complete step by step document for configuring the idoc to file scenario along with ALE Settings
To Configure the IDOC TO FILE SCENARIO,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1)   Create an RFC Destination to the Sending System in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a)   Select create new button
b)   Enter the port name as SAP+SID (The starting char should be SAP)
c)   Enter the destination client
d)   Enter the RFC Destination created in SAP R/3 towards other system
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h)   Test the connection and remote logon.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(We21)
a)   First Select Transactional RFC and then click create button
b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Outbound Parameters (WE20)
a)   Create New
b)   Create the Partner no. name as same the logical system name of the destination system
c)   Select Partner type LS
d)   Enter details for Type: US/USER, Agent, and Lang
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I)   save
4)   In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
5)   Create Customer Distribution model in the transaction code BD64
1)   Click on the Create modal View button and enter the short text, Technical name etc as shown below
2)   Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3)   Save the Distribution model
    Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
    It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
    Then, you will be intimated about the partners, port creation, and outbound parameters creation
4)   Distribute Customer Distribution Model
    In the menu item GO to Edit->Modal View-> Distribute to the destination client
    Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
             Step2:Repository
1)       From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2)       Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
         From the list of Software Component Versions, Choose your own software component version .Click Import.
3)       On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
         Your NameSpace is urn : DSZVFGD
4)       Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
         After this specify the connection parameters to the R/3 system:
4.1)     System :SAPFOX
4.2)     Client :800
         Then Save it. The new namespace will be visible under software component version node in the left frame.
         Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3)     Application server:172.25.5.7
4.4)     System number:00
4.5)     User name: DEVELOPER
4.6)     Password: Password of Sap R/3 system.
         Then click continue .You will find IDOC node. Click on this node and select the   Idoc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the    Idoc will be available into XI as Message types. So no need to create any Idoc Structure. We need to create a structure for file only.
5).      Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6)        Create new data types.
6.1)      Right click on Data types and select New.
           Your Data Type is :DT_FILE
          In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
          Save the object.
6.2)      The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
          no need to create Data types. They are imported directly as Message types.
6.3)      To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
          Select the following.
6.3.1)    Category: XSD.
6.3.2)    Messages: From All Available Global Elements.
6.3.3)    File:
          Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7).      Create a new Message Type.
7.1)     In the left hand frame under Interface objects, right click on the Message types and select new.
7.2)     Give a suitable name to the Message type.(MT_ messagetype).
7.3)     For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
         Save it.
8).     Create a Message interface
8.1)    In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2).   The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
        Save it.
9) .    Create a graphical mapping between the target document and the sender .
9.1)    In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2)    As Source message select your own Idoc .You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- >     Namespace->Imported Objects.
9.3)    As Target Message you can choose your Message type .Choose Search for Integration Object.
9.4)    Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5)    Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the   Source fields to the respective Target Fields.
        Save It.
9.6)    You can also Test your Mapping by selecting the 'Test Tab'.
9.7)    Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10).     Create an Interface Mapping.
10.1)   In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2)   Source interface : Your Outbound Interface (The Source document(Idoc) interface).You can Choose Search for Integration Object.
10.3)   Target interface:    Your Inbound Interface( The Target document interface).
        Then Select 'Read Interface' and Assign your 'Mapping Program' .
        Mapping Program: Your Message mapping.
        Then Save it.
11.)    Finally , in the left hand frame ,go to your change list and Activate it
           STEP 3: Directory
1)      From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
        Create a Scenario Object
2).     The First Step is to create a Scenario Object
        This will serve as container for all your configuration work. Create and save a scenario object
3)      In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4)      In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) .    Create a Communication Channel.
6).     Expand your service and right click on Communication Channel. Name your Communication Channel
        Here we need to configure the adapter.
     Since The Sender is IDOC , then there is no need of Sender communication channel and Sender Agreement.
          For the Receiver, Specify the following Parameters
6.1       For the adapter type , use the F4 help and select FILE.
6.2       Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3       Specify the following parameters.
          Transport Protocol: File Transport Protocol.(FTP)
          Message Protocol: File Content Conversion(since the xml file produce by XI need to be converted to text file)
          Adapter Engine: Integration Server
          For the File system access Parameters, enter the following
          Source Directory:VILAS
          File Name: Input.txt
6.4       For the FTP Connection Parameters, Specify the Following
          Server: 172.25.7.116
          Port: 21(by default)
          Data Connection: Passive
          Connection security: None
          Connection Mode: Permanently
          Transfer Mode: Binary
6.5       For Processing Parameters, Specify the following
          File construction mode: Add Time Stamp
          File Type: Binary
6.6       For Content Conversion Parameters, Specify the Following
          RecordSet Structure:
          Adapter Status: Active
          The receiver file adapter is now configured. Save your Communication Channel.
           Create an Receiver Determination.
7).       From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1)      Select your sender service and interface.
          Sender:
          Party: blank
          Service: Sender service(Business system)
          Interface : Sender interface
7.2)      In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
            Create an Interface Determination.
7.3)       Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1)     In the Receiver Determination   you just created, have a look at the area Configuration Overview for Receiver Determination   at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2)     In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
           Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3)     You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
           After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4)     A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5)     When you are done , Save the Interface determination object.
8.)         Create a Sender Agreement.
           In the left hand frame , right click on Sender Agreement ->New
8.1)       Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Outbound Interface
8.2)       In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.)         Create a Receiver Agreement.
           Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1)       Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2)       In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
           Specify the following:
           Party: blank
           Service: Select your own Business system
           Interface: Inbound Interface
9.3)       In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
           Your Configuration is complete. Activate the objects.
PLZ REWARDS POINTS
VIKAS

What are exercise steps for RTI scenario

hi,
we have configured AII and EM using RTI scenario configuration guide.
To run the scenario in a systmatic way, is there any any instruction booklet containing steps and the transactions. like go to this system and do this, go to that system and do that.
regards,
thanks in advance,
Sathyanag

hi,
The configuration Guide available for RTI processing in AII 4.0 should have enough information to help you out.
regards,
arul sekar.

Need Message Type Creation Steps for Different Scenarios

Hi Friends,
I have done following steps for Outbound IDoc [Extended IDoc]
1. Create custom Message Type                           WE81
2. Create custom Segments               WE31
3. Create IDoc Extension               WE30
4. Create IDoc Type [Basic+Extu2019n]          WE30
5. Link Custom IDoc with Message Type          WE82
6. Activate CP for Custom Message Type                     BD50
7. Activate Change Pointers globally Flag on     BD61
8. Maintain custom message type in CDM                     BD64
9. Define partner profile for custom msgtype                    WE20
After completion of the above steps.
I am unable to do the following steps.
10. Checking the IDoc Creation                          BD10
          or
11. Execute CP IDoc generation Program     RBDMIDOC
Here these steps I am unable to find Message Type.
If we create message type thru BD53 [std idoc] it will come.
but my situation is for extended IDoc I need to create message type.
If any one worked on this situation Help me out.
Regards,
Mutyapu4u.
Edited by: naveen mutyapu on Jun 24, 2008 2:51 PM

Hi,
Check the link below:
http://www.****************/Tutorials/ALE/ALEMainPage.htm
Hope this helps..
Regards,
Sharath

Steps for IDOC scenario

Hi all,
I am doing an File to IDOC scenario.I have done with all the mappings and configurations in IR and ID.Please can anyone let me know the configurations that are to be done in R/3 and SLD for the posting of IDOC.
Please can anyone explain this to me.
Awaiting for ur reply
Amit

Hi Amit,
the following is from a thread/blog I cant find anymore. So I copy and pasted it!
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Regards Mario

XI Whitepaper on practical scenarios and capabilities?

Hi All,
I am looking out for a an XI Whitepaper which has some crisp details about what can be done with XI. Maybe what scenarios are best served with XI. ( Have seen glossy SAP slides, but want some practical advise/details which can be implemented technically)
Curently this forum has wealth of information about HOW-TO-Implement technical details, but I failed to find many threads which talk about what all scenarios its possible to accomplish with XI..like file-to-file, xml-to-IDOC , XI connecting to www, or internet to XI, etc etc. I am interested in knowing the scenarios/capabilities and an TYPICAL issues that we might face in these scenarios.
I am fairly a newbie to XI so wanted to know XI more in broader perspective rather than just a File-to-Idoc kind of software
So am just trying to weigh in the perspective/ knowledge about XI at a broader level rather than an How-to approach . Hope you experts can throw some light on this.
Many thanks
Shirin

Hi Shirin,
Did you ever look the[ XI Wiki |https://wiki.sdn.sap.com/wiki/display/XI/Home]page
Do see that you can find the stuffs that you obviously look for.
Also have a look at this [Step-by-Step Guides|https://wiki.sdn.sap.com/wiki/display/XI/Step-by-Step+Guides].
Thanks
SaNv...
PS: Also have a look at the children pages that are linked with the wikis.

Singleton node and non singleton practical scenario

Hi Friends,
Iam totally confused with singleton and non singleton node implementation please explain practical implementation on singleton and nonsingle ton node . In which scenario non single ton node is used.
Thanks in advance
Prasad

Hi,
Singleton Node:
A singleton node contains only one instace of the node at runtime. And that instace contains multiple elements at runtime.
By default if we create a node under ROOT context node, it will be allways singleton true.
Non singleton node:
A non singeton node contains more then one node instance at runtime. And each instance contains multiple elements at runtime.
It is not possible to create NonSingletonNodes directly under ROOT context node. We can create under any node which is under ROOT context node.
Note: In terms of datastorage at runtime we can say if node is table then each elment of node instance is a row of that table.
When is it requried to create non singleton nodes?
For example if you have list of SalesOrders and each and every oder is having list of items. Then we can create this node structure in two ways:
Orders (singleton true)
> Items (singleton true)
Here in this case at any point of time the there will be only one instance of Items node exist for currently selected element of Orders node. And that instance contains multiple elements nothing but items of that order.
Orders (singleton true)
> Items (singleton false)
Here in this case at any point of time all the instances of Items node exist for all the elements(not only for currently selected element) of Orders node. And those instances contains multiple elements nothing but items of those corresponding orders.
I hope it helps.
Regards,
Vijay K

SCM Best Practice Scenarios - can't find them on Service Marketplace

I'd like to run Best Practice SCM scenarios such as:
     S24 Vendor-Managed Inventory
     S41 Supplier-Managed Inventory
     S51 Available-to-Promise with Product Allocation
but can't find them anywhere.
In version SCM 5.0 they could be located in the Best Practice Area, but the links are missing now. When I go to the Industry Specific Best Practices (i.e. for Vendor-Managed Inventory), all I see is scenarios related to ECC 6.0.
Thanks in advance for any help locating these.

Chris,
Small world. I live out in Chester county.
BPPs can be lengthy and sometimes take a while to load. They are in MS word format, so you must have a way to read MS Word docs. Also, our friends in Waldorff don't always have their servers up. Sometimes it helps to try again later, or during a period of low activity. I usually have good luck during late afternoon and early evening EST time zone.
Here are some links. I haven't tied to load all of them, but I was successful in the first four. Give it a shot.
http://help.sap.com/bp_scmv250/documentation/S24_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S35_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S37_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S38_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S39_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S40_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S41_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S45_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S46_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S47_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S48_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S51_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S52_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S53_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S66_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S68_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S70_BPP_EN_DE.doc
http://help.sap.com/bp_scmv250/documentation/S72_BPP_EN_DE.doc
Rgds,
DB49

Step by Step XI practical scenarios

Similar Messages

Maybe you are looking for