TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and

Hi All
Can anyone pls give me all the TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and BAPI
Thanks
ss

Hi SS..
    SM59-For creating the RFC destination
    we21- For ports
    we20-Partner profiles.
For more inforamtion Please look at the below information:
<b>SAP XI</b>
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 XI 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.
<b>SAP R/3</b>
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 <b>SLD</b> – 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.
   Thanks and Regards,
   Chandu.
Message was edited by:
        Chandu
null

Similar Messages

  • Taking Dump of Ports, Partner Profiles etc before Client Deletion

    Hi,
    Let me firstly tell you about the requirement.
    I need to delete a 9TB client using TDMS. And then re-create it again for users. Now the problem is , that the Partner Profiles, Ports will be deleted when I delete the client, which I cannot afford to loose are there are a lot of them.
    So, what is the best way to take a dump of the ports and partner profiles and other relevant things. I tried taking the table entries into transports and thought of re-importing them. But I'm not sure what all tables will be there as there are many like :
    EDPP1 (general partner profile),
    EDP12 (Message Control),
    EDP13 (outbound parameters)
    EDP21 (inbound parameters)
    Partner function exists in table TPAR
    Outbound process code exists in table TEDE1
    Logical message type exists in table EDMSG
    Process code exists in table TEDE2
    What is the table for Basic Idoc type
    Port is defined in table EDIPORT  but where is their assignment to the Logical Name its not in this table.
    There would be so many tables that are interdependent and I don't wanna loose even a single one of them.
    Please advice the best option,  as I am nearing the deadline to delete this client.
    Your help is really appreaciated.
    Thanks.

    Hi
    Iam adding some pots to the above which may help you Take screenshots for some important Settings / Configurationsso that you can easily restore them afterclient  refresh. For example
    u2022     TMS Configuration (STMS)
    u2022     Printer Settings (SPAD)
    u2022     Logon Group (SMLG)
    u2022     OP Mode (RZ04)
    u2022     RFC Destinations (SM59)
    u2022     WE20 u2013 Partner Profiles
    u2022     WE21 u2013 Ports in IDOC Processing
    u2022     Client Definitions (SCC4)
    u2022     Logical System Names (SCC4 and SM30: V_TBDLS)
    u2022     E-Mail Configuration (SCOT)
    u2022     SAP House-Keeping Jobs and Customeru2019s Jobs (SM37)
    u2022     SSL Configuration (STRUST) if using
    u2022     Others
    Se09 other request u2022object list Enter R3TR  TABU  RFCDES
    Regards

  • Idoc to File. Partner type as 'KU' and 'LI'.. Acheivable w/o using Party's?

    Hi all,
    Idoc to File scenario.
    I have the receiver partner type as 'KU' and sender partner type as 'LI'.
    I want to create the scenario without using party for these partner Types.
    Is it possible for me to create the B2B scenario without using party's?
    Is it mandatory that we need to use partys and Identifiers for these kind of scenarios?
    Kindly let me know if anyone has idea on this.
    Thanks
    -Seema

    Hi Seema,
    I appreciate that you chose to go with the parties
    That should be called a good design decision.......
    Now answering your query regarding the party identifiers
    Idoc to File :
    <SNDPOR>SAPDL1</SNDPOR>
    <SNDPRT>LI</SNDPRT>
    <SNDPRN>90000</SNDPRN>
    <RCVPOR>SAPXI</RCVPOR>
    <RCVPRT>KU</RCVPRT>
    <RCVPFC>SP</RCVPFC>
    <RCVPRN>36</RCVPRN>
    For Sender Party (say party INTERNAL)
    Agency : LD1_001
    Scheme: ALE#LI
    Name: 90000  (vendor number set in WE20 in the R/3)
    For Receiver Party (say party EXTERNAL)
    Agency: LDI_001 (SID_<client> BS as defined in SLD)
    Scheme: ALE#KU#AG  (AG for partner function SP)
    Name: 36  (customer number set in WE20 in the R/3
    This will resolve the IDoc header data into the following XI SOAP header information:
    Sender Party - INTERNAL
    Sender Service - LD1_001 (say this is the business system defined for logical system SAPLD1
    Receiver Party - EXTERNAL.
    Though, you can determine the receiver party alongwith the Receiver Service later at RCV DETERMINATION step, as I have said earlier.
    Yes, for outbound you have to maintain the identifiers for Sender Party type LI, but you can still skip the Receiver KU type and update the SOAP header at RCV DET step.
    File to Idoc:
    <SNDPOR>SAPXI</SNDPOR>
    <SNDPRT>KU</SNDPRT>
    <SNDPRN>36</SNDPRN>
    <SNDPFC>SP</SNDPFC>
    <RCVPOR>SAPDL1</RCVPOR>
    <RCVPRT>LS</RCVPRT>
    <RCVPRN>MAINSAP</RCVPRN>
    For Sender Party (say party INTERNAL)
    Agency: LD1_001 (SID_<client>)
    Scheme: ALE#KU#AG
    Name: 36
    For Receiver Party (say party EXTERNAL)
    Because the RCVPRT value is LS , no need to set the Receiver Party for that.
    But if you want to have some Receiver Party value for the same you can use Header Mapping in receiver agreement.
    Mandatory Setup in Receiver IDoc Adapter:
    Set the indicator -  Apply Control Record Values from Payload
    Remember to set the Identifiers in the Identifiers Tab in Idoc channel.
    Sender:
    Agency : LD1_001       Scehma : ALE#KU#AG
    Receiver:
    Agency: LD1_001        Schema : ALE#LS
    I am not sure why this ALE#LS entry is required, but according to my experience if we don't have that entry, the Idoc Adapter throws error while converting the Receiver Party (considering you use party in the ID configuration for both Sender and Receiver).
    Yes you are right, you can hard code the SNDPRN, RCVPRN values in the mapping and can take the values from payload...........for that set the following Indicators in Idoc channel:
    Take Sender from Payload
    Take Receiver from Payload
    Let me know if you have any concerns or any additional observation you make while configuring the scenarios. Thanks.
    Regards,
    Suddha

  • IDOC status 30 but partner profile is set to send immediately (04)

    Hi guys,
    I have a problem with idocs not being sent immediately... The outputs, the EDI partner profiles are all set up correctly...
    it is configured to send immediately however, it's not doing so... prior to upgrade to ECC 6.0 it's working fine... now its not...
    However, in BD87 thru manual release of IDocs, it is working fine...
    Is there any changes to ECC 6.0 for this matter? or is there anything that needs to be set up other than those mentioned above in order for it to work in ECC 6.0?
    Thanks a lot!

    Mark, have you looked at the OSS notes? By 'IDOC status 30' it finds 300+ notes, this is really a wide-spread issue.
    The most recent one is 150202, which actually recommends collecting the IDocs instead of having "send immediately" because it saves the RFC resources. This is not really an ABAP issue, so you might want to discuss this with your Basis admin.
    Also, from my experience, even with "mission critical" processes the users, in fact, never feel any real difference between "immediate" and 5-10 min. Sometimes (due to a technical problem, for example) nothing goes on for 30+ min. and no one even notices.

  • Receiving IDoc SYPART01 (Transfer of partner profiles)

    Hi, well this is not a special PI issue but we have the problem to receive the SYPART01-Idoc in target system.
    This is due to not knowing the process code for inbound processing in target system. We already used BAPI, searched for Function Modules etc. - but with no success.
    How do you guys transport partner profiles from one client or system to another?!
    Or does someone know how to manage the inbound processing for IDoc SYPART01 ?!
    br Fritz

    Hello,
    Any news on this subject ? I'm interested by this topic.
    I noticed there must be some specific FM in Emmanuel Hadzipetros SAP Press book.
    I guess there aren't any "standard" way !?
    I tried to figure out something and notice in the SED package that there are RFC FM like EDI_AGREE_PARTNER_INSERT, maybe we could find out a LSMW solution.
    Jon

  • Interaction between Distribution model, partner profile, etc.

    Hello,
    I am a newbie in the SAP world, and I am a little bit lost in the behavior of the Outbound Processing (the send of an IDoc to an external non-SAP system).
    Actually my question is how the following components interact during an outbound process :
    - RFC Destination
    - Logical Port
    - Logical System
    - Partner Profile
    - Distribution Model
    - SAP Gateway
    - IDOC Repository
    - ALE Service
    Currently, the only thing I think I have really understood is that the RFC Destination allows to hide to SAP the Program ID of the registered external server...
    Thanks a lot
    Sebastien

    For each logical system and each basic message type (for example, LOIBOM), a unique message type has to be defined by reducing the original one (for example, MYBOM).
    If you reduce a message type, only the obligatory fields are automatically selected. You must select those segments and fields you want to have transferred. Fields that have not been selected for transfer always contain the value "/".
    Maintain partner profile
    Each of the message types of the customer distribution model (see above) must be assigned to the partner profile. Enter the receiver port (see above), package size, output mode and IDoc type in the detail screen of the receiver port. You must also define whether the IDocs should be sent immediately, or if they should be collected first.
    Maintain customer distribution model directly
    First define a customer model for a logical R/3 system. The displayed list shows which logical system is the sender and all the possible receiving systems that have been defined. "Create message type" defines which logical system receives information from the logical R/3 system.
    When maintaining the customer distribution model, you usually add all (reduced) message types that should be sent from the R/3 system to the external system.

  • Does Anybody know the Errorcode 196619 in relation to standard 2 port NI CAN Controller, LabVIEW 6i and WIN NT 4 - SrvPck 6.

    Frequently the WIN NT 4 System hangs up when I start a LabVIEW Can Application. ( i.e. the NI CAN Examples.)
    If I'm able to start the application it works propperly. I'm using the two ports of the PXI CAN Controller to test the communikation. ( CAN0, CAN1 )

    Be sure that the card is plugged in tight. Do any other PXI cards work in the chassis? If not, there may be something wrong with the PXI hardware.
    Also, be sure to install the latest CAN drivers from ni.com.
    Randy Solomonson
    Applications Engineer
    National Instruments

  • Need a Clarification in defining a Partner Profile

    Hi Experts,
    I have a requirment wherein i need to send delivery idoc delvry01 for all the deliveries created for a shipping point.
    I have created a output type ZLD0 and has Shipping point as the access seq. I have maintained condition records for the shipping point to create idocs for.
    I have created partner profile with the logical system. But its not working.
    Is there anyway to trigger idoc on the delivery document by not defining each and every customer on the partner profile.
    i mean to say in this case how to create the partner profile, is it with logical system or Customer number. if it is with customer number, if i have 1000 customers, creating 1000 Partner profiles is doesn't make sensce...
    Please clarify this...
    Thanks in Advance
    Narendra.

    I haven't done this for deliveries but we did something similar for the Purchase Orders, so maybe this will give you some food for thought.
    We defined one Logical System per Purchasing Organization. Unfortunately, the PO output could not have been assigned to the 'logical system' partner type. So what we ended up doing - we created a new outout type ZNEU (copy of standard NEU) and set up access sequence Doc.Type / Purch. Org. / Vendor. Then in MN04 for this option we added a record for each Purchasing Org (EKORG) and all the applicable Vendor Numbers. It is pain in the back but it's much faster than creating individual profiles.
    Now when I look at the PO output there is a line with ZNEU and vendor # as a partner but when I run RSEOUT00 I get an IDoc for the whole Purchasing Org.
    So replace Purch. Org with Shippint point and Vendor with Customer and it's pretty much your scenario. I'm not sure what's the SD transaction similar to MN04, try VV31.
    Good luck!

  • LSMW: ALE/IDOC, getting the Create a partner profile for message type

    Hi Gurus,
    In my current project, i need to upload the employee data using the ALE/IDOC method with the LSMW
    when i'm generating the idoc in the 13th step, its posing the information message stating that:
    Create a partner profile for message type 'ZEMP_MSG'
    In partner profile i already assigned the message type .
    How to solve this issue, <inappropriate urgency removed by moderator>
    Thnks&regards,
    sree
    Edited by: Thomas Zloch on May 13, 2011 9:55 AM

    This forum's aim is not only to search for information and ask the members questions, but also to share knowledge. When you have asked a question and found a solution, do share with the rest.

  • Steps for Idoc to EDI Subsystem

    Hi all,
    Can anyone tell me the steps that i have to worry about to send an idoc immediately to EDI Subsystem
    I mean what all things i have to specify while creating ports and partner profiles etc
    Thanks

    Sending Order Confirmations by EDI (SD-SLS) 
    Use
    By setting up and using the Electronic Data Interchange functions in the R/3 System, you eliminate the need to print documents and send them through the standard mail system. Instead, you send the information electronically. This method is more practical, convenient, and allows you and your customer to process data faster.
    In this EDI scenario, you process and send order confirmations to a customer's R/3 Purchasing system.
    Prerequisites
    Application
    Customizing
    To process outbound order confirmations, you need to make all of the necessary EDI settings in Customizing for Basis. You make settings for output control in Customizing for Sales and Distribution.
    Output Control
    The standard SD condition components are:
    Condition component     Value
    Sales document type     AA
    Output determination procedure     V10000
    Condition type     BA00
    Transmission medium     6 (EDI)
    Access sequence     0001
    Processing subroutine     Program RSNASTED, form routine EDI_PROCESSING
    Partner function     SP (sold-to party)
    Application     V1
    Condition records for outbound order confirmations are maintained in Customizing for Sales and Distribution. Choose Basic Functions  Output Control  Output Determination  Output Determination Using the Condition Technique  Maintain Output Determination for Sales Documents.
    IDoc Interface
    Define the EDI partner profile for your partner (transaction WE20) by entering the following data for the outbound parameters for partner profiles and the additional profiles for message control:
    Field     Value
    Message type     ORDRSP
    Partner type     KU (customer)
    Partner function     SP (sold-to party)
    Receiver port     e.g. SUBSYSTEM
    Output mode     e.g. Transfer IDoc immediately
    Basic type     ORDERS04
    Process code     SD10
    Activities
    Create an order. When you save the document, the system uses your settings in output control to find the appropriate condition record and send confirmation of the order by EDI. To review and maintain output data in the document, choose Extras  Output  Header.
    Receiving Acknowledgments via EDI (MM-PUR-GF-CON) 
    Use
    You have arranged with your vendor that that latter is to send you acknowledgments in respect of purchase orders or outline agreements received from your company. (Note: both kinds of acknowledgment are generally referred to as "order acknowledgments" in the system. The corresponding EDIFACT term is "order response" (ORDRSP).)
    You have the option of working exclusively with acknowledgments. The acknowledgment is then purely informative in nature, since only the acknowledgment number is recorded in the system.
    If you wish to receive different kinds of vendor confirmation, such as both order acknowledgments and shipping notifications (also known as advance shipping notices - ASNs), it is possible for quantities and dates to be entered in the system automatically).
    For more information on this topic, refer to the MM Purchasing documentation ( Confirmations from the Purchasing Viewpoint and Receiving Confirmations via EDI).
    Prerequisites
    Application
    To work with several categories of vendor confirmation, you must:
    u2022     Enter a confirmation control key on the item detail screen
    u2022     Set up the confirmation control facility in Customizing for Purchasing (Purchasing  Confirmations  Set up Confirmation Control). There you can specify the order in which you expect confirmations from your vendors, for example.
    Under Confirmation sequence, you can:
    u2022     Specify tolerances for date and price checks
    u2022     Allow vendor material changes (VMat indicator)
    u2022     Adopt vendor price changes (Price indicator)
    Do not use a confirmation control key if you work exclusively with acknowledgments.
    IDoc Interface
    You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  EDI  Set up Partner Profile):
    Parameters for Inbound Messages     
    Field     Value
    Partner type     LI
    Partner role     LF
    Message category     ORDRSP
    Process code     ORDR
    Processing     Initiate immediately or process via background program
    Activities
    When an acknowledgment is received in the form of an incoming EDI message, the system checks whether a confirmation control key has been entered in the relevant PO or outline purchase agreement.
    u2022     If there is no confirmation control key, only the acknowledgment number is entered on the item detail screen.
    u2022     If there is a confirmation control key, the system updates the confirmation overview. That is to say, the dates and quantities set out in the acknowledgment that has just been received are recorded and taken into account in the overview. To view acknowledgments that have been received, choose Item  Confirmations  Overview from the item overview. Column C (creation indicator) contains the value 3, meaning that the acknowledgment was received via EDI. The system also enters the IDoc number in the External document column.
    An IDoc can always acknowledge one purchase order only. The acknowledgment relates to the PO item, not to any individual schedule lines.
    Exceptions
    When an acknowledgment is received via EDI, the system automatically checks quantities, prices, and dates. In checking quantities, it applies the over- and underdelivery tolerances set for the item. You can set tolerances for prices and delivery dates in Customizing for Purchasing under Set up Confirmation Control.
    The tolerances you define apply to all vendors. Using the enhancement MM06E001 provided by SAP, you can specify that the tolerances do not apply to certain vendors.
    If the acknowledged quantities, prices, and dates vary from those set out in the PO or purchase agreement, the system issues a warning message. In this case, the purchasing document is not updated.
    For more information on this topic, refer to the section Error Correction (Receiving Confirmations via EDI) of the MM Purchasing documentation.
    Sending PO Change Notices via EDI (MM-PUR-PO) 
    Use
    This section describes how to transmit a change notice relating to a purchase order that has already been sent to a vendor.
    The function corresponds to the transmission of a purchase order via EDI.
    Prerequisites
    Application
    You have already successfully transmitted the original purchase order to the vendor via EDI.
    Message Control
    You have created message condition records for your EDI vendors (Purchasing  Master data  Messages  Purchase order  Create).
    Use the message type NEU to transmit PO change notices.
    IDoc Interface
    You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  Set up Partner Profile):
    Parameters for Outbound Messages     
    Field     Value
    Application     EF ( Purchasing: purchase order)
    Message category     ORDCHG
    IDoc type     ORDERS02 or ORDERS04
    Process code     ME 11 (ORDCHG: PO change notice)
    If you wish to transmit PO conditions or texts to your vendor, you must create an IDoc view. For more information on this topic, see Sending a Purchase Order via EDI.
    Activities
    Change an existing purchase order via Purchasing  Purchase order  Change. Make the necessary changes and save the PO.
    The new message is compared with the last successfully transmitted message. PO change notices indicate whether any new items have been added to the PO, and/or whether any already transmitted items have been changed.
    When the message is transmitted, only those changes that are simultaneously new and print-relevant are included. The system sets the change indicator for the new message. To check the change indicator, choose Header  Messages in the PO item overview.
    See also:
    MM Purchasing: Creating a Purchase Order
    Cross-Application Components:  Customizing Message Control in Purchasing (MM): Example: Purchase Order
    Receiving Order Changes by EDI (SD-SLS) 
    Use
    In this EDI scenario, you receive and process order changes sent by a customer from an R/3 Purchasing system.
    Prerequisites
    Application
    General
    You can receive and process order changes in your system only on the basis of an existing order.
    Customizing
    To process incoming order changes, you need to make all of the necessary settings in Customizing for Basis. There are no special settings for Sales and Distribution.
    IDoc Interface
    Define the EDI partner profile for your partner (transaction WE20) by entering the following data in the header and detail screen for inbound parameters:
    Parameter     Value
    Partner type     KU (customer); if the IDoc is sent from an R/3 system via tRFC (in a typical case with ALE scenarios), enter LS for logical system!
    Message type     ORDCHG
    Process code     ORDC
    Processing     Process immediately
    Allowed Agents     Enter an R/3 user or an organizational unit, for example.
    Activities
    Inbound Processing
    The IDoc interface receives the IDoc and reviews its control record. According to this record and the corresponding partner profile, the IDoc is transferred to the function module IDOC_INPUT_ORDCHG in Sales and Distribution. The ALE services are called.
    The system processes the IDoc in the background, using the data records in the IDoc to determine the relevant order.
    If processing is successful, the system updates the sales order. The IDoc is sent back to the IDoc interface which updates the status records in the IDoc.
    Exception Handling
    If it cannot determine an order, or if an error occurs in processing, the system determines the relevant agent(s) and sends a workitem to the integrated inbox(es). An agent can pick up the workitem to process the IDoc or simply end processing.
    To display an IDoc for order changes, choose Environment  Display facsimiles in the order. The system displays a dialog box of object links where you can choose Linked IDocs.

  • Need all transaction codes for idocs

    need all transaction codes for idocs

    Hi,
    ALE IDOC
    Sending System(Outbound ALE Process)
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Create Model View
    Tcode BD82 ? Generate partner Profiles & Create Ports
    Tcode BD64 ? Distribute the Model view
    Message Type MATMAS
    Tcode BD10 ? Send Material Data
    Tcode WE05 ? Idoc List for watching any Errors
    Receiving System(Inbound ALE )
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 ? Idoc List for inbound status codes
    ALE IDOC Steps
    Sending System(Outbound ALE Process)
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Create Model View
    Tcode BD82 !V Generate partner Profiles & Create Ports
    Tcode BD64 !V Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 !V Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 !V Send Material Data
    Tcode WE05 !V Idoc List for watching any Errors
    1)a Goto Tcode SALE
    Click on Sending & Receiving Systems-->Select Logical Systems
    Here Define Logical Systems---> Click on Execute Button
    go for new entries
    1) System Name : ERP000
    Description : Sending System
    2) System Name : ERP800
    Description : Receiving System
    press Enter & Save
    it will ask Request
    if you want new request create new Request orpress continue for transfering the objects
    B) goto Tcode SALE
    Select Assign Client to Logical Systems-->Execute
    000--> Double click on this
    Give the following Information
    Client : ERP 000
    City :
    Logical System
    Currency
    Client role
    Save this Data
    Step 2) For RFC Creation
    Goto Tcode SM59-->Select R/3 Connects
    Click on Create Button
    RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
    give the information for required fields
    RFC Destination : ERP800
    Connection type: 3
    Description
    Target Host : ERP000
    System No:000
    lan : EN
    Client : 800
    User : Login User Name
    Password:
    save this & Test it & RemortLogin
    3)
    Goto Tcode BD64 -- click on Change mode button
    click on create moduleview
    short text : xxxxxxxxxxxxxx
    Technical Neme : MODEL_ALV
    save this & Press ok
    select your just created modelview Name :'MODEL_ALV'.
    goto add message type
    Model Name : MODEL_ALV
    sender : ERP000
    Receiver : ERP800
    Message type :MATMAS
    save & Press Enter
    4) Goto Tcode BD82
    Give Model View : MODEL_ALV
    Partner system : ERP800
    execute this by press F8 Button
    it will gives you sending system port No :A000000015(Like)
    5) Goto Tcode BD64
    seelct the modelview
    goto >edit>modelview-->distribute
    press ok & Press enter
    6)goto Tcode : BD10 for Material sending
    Material : mat_001
    Message Type : MATMAS
    Logical System : ERP800
    and Execute
    7)goto Tcode : BD11 for Material Receiving
    Material : mat_001
    Message Type : MATMAS
    and Execute --> 1 request idoc created for message type Matmas
    press enter
    Here Master Idoc set for Messge type MATMAS-->press Enter
    1 Communication Idoc generated for Message Type
    this is your IDOC
    Change Pointers
    I know how to change the description of a material using ALE Change Pointers.
    I will give the following few steps
    1) Tcode BD61---> check the change pointers activated check box
    save and goback.
    2) Tcode BD50---> check the MATMAS check box save and comeback.
    3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
    4) Tcode BD52---> give message type : matmas press ok button.
    select all what ever you want and delete remaining fields.
    save & come back.
    5) 5) go to Tcode MM02 select one material and try to change the description and save it
    it will effects the target systems material desciption will also changes
    6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
    give Message type : MATMAS and Executte
    ALE/IDOC Status Codes/Messages
    01 Error --> Idoc Added
    30 Error --> Idoc ready for dispatch(ALE Service)
    then goto SE38 --> Execute the Program RBDMIDOC
    29 Error --> ALE Service Layer
    then goto SE38 --> Execute the Program RSEOUT00
    03 Error --> Data Passed to Port ok
    then goto SE38 --> Execute the Program RBDMOIND
    12 Error --> Dispatch ok
    Inbound Status Codes
    50 Error --> It will go for ALE Service Layer
    56 Error --> Idoc with Errors added
    51 Error --> Application Document not posted
    65 Error --> Error in ALE Service Layer
    for 51 or 56 Errors do the following steps
    goto WE19 > give the IDOC Number and Execute>
    Press on Inbound function Module
    for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
    BAPI tcode --- BAPI.
    Also:
    IDOC:
    IDOC ADMINISTRATION
    WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
    WE05 View IDocs
    WE60 IDoc type documentation tool
    WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing.
    BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
    1.4 IDOC DEVELOPMENT
    BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations.
    WE19 EDI test tool. Use to test inbound Function module changes.
    WE31 Segment create
    WE30 Create IDoc extension type
    WE82 Link Release detail to Extension IDoc Type
    WE57 Assign function module to logical message and IDoc type
    BAPI: BAPI, SWO1.
    Transaction codes Related for IDOC Configurations
    WEDI: Area Menu for IDOC’s
    WE02: Display IDoc
    WE19: ALE Test tool
    WE30: Development of IDOC Type
    WE31: Development of IDOC Segment
    WE41: Process Codes, Outbound
    WE42: Process Codes, Inbound
    WE47: Status Maintenance
    WE81: Logical Message Types
    WE57: Assignment Messages for Appl. Objs
    SM59: RFC Destinations (Display/Maintain)
    SALE: Display ALE Customizing
    BD54: Maintaining Logical Systems
    BD67: Maintain methods (inbound)
    BD64: Maintenance of Distribution Model
    BD87: Status Monitor for ALE Messages
    Reward points if found helpful...
    Cheers,
    Chandra Sekhar.

  • Inbound Idoc processing issues - Partner Profiles - error status 56

    Hello All,
    I'm having a little difficulty posting an idoc coming from MDM.  It's a CREMDM04 xml coming from an MDM system.  It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs.  The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe).  I'm using nothing but standard mapping/material from the SAP Business Content for XI.  After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
    The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
    The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc.  How is the RCVPRN value being populated? 
    SOAP Header in IDocOutbound tag
      <SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
      <SAP:RCVPRN>[String Value]</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
    I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere.  Perhaps i'm just overlooking it?
    When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
    Any help is very much appreciated! :-D

    Hi Jason ,
    Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
    To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
    STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
    We need to do the following settings in XI
    1) Create an RFC Destination to the Receiving 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 XI towards R/3
    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 Inbound 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 Inbound Parameters.So click on ADD TO Create Inbound Parameter
    g) Select Message type
    h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
    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
    do let me know if it helped
    Edited by: Tom  Jose on Feb 21, 2008 9:04 AM

  • Examples needed for Idoc to file and IDOC to web services

    Hi ,
    Could any one of you give some examples which take me through step-by-step in building IDOC-TO-FILE and IDOC-TO-WEB SERVICES?
    Regards,
    XI Developer.

    Hi,
    For IDOC scenario you need to first do the required configuration:
    ALE configuration for pushing idocs from SAP to XI
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    Testing purpose u can use the below method:
    IDOC testing using WE19
    /people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters --> For Idoc sender: IDOC -file
    IDOC configuration:
    Please follow the below process for configuration:
    Pre-requisites for Inbound IDoc to R/3 from PI:
    Configuration required at Xi side:
    Go to IDX1: configure the port.
    Go to IDX2: load the DOC metadata.
    Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
    Configiration required at R3 side:
    Maintain Logical System for PI (SALE transaction):
    Maintain Partner Profile for XI system(WE20):
    Pre-requisites for Outbound IDoc from R/3 to PI:
    Configurations required in R/3:
    Maintain Logical System (SALE)
    Define RFC Destination (SM59) which points to PI system
    Maintain Port (WE21)
    Maintain partner profile. (WE20):
    Maintain Distribution Model (BD64):
    File To IDOC - Part1 (SLD and Design):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
    File To IDOC - Part2 (Configuration):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
    File To IDOC - Part3 (Steps required in XI and R3):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    SOAP scenario:
    YOu have to first create the WSDL through ID and import that WSDL in to IR external definition.
    Refer the below thread and pdf:
    How to use SOAP adapter:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
    SAP AII - How to consume and expose webservices  ?
    Thnx
    Chirag
    reward points if it helps.

  • IDOC is Getting Fail with - 56 Status EDI Partner profile not available

    Hi,
    I am trying to Post invoice Data into IDOC on ECC Side.
    My Scenario is File u2013 XI u2013 ECC(IDOC).
    But It is Getting Fail with 56 Status u201C EDI: Partner profile not available u201C
    On Control record I am getting this
    Port                       BLANKKKKKKKKKK
    Partner Number              CLNTDEC110      Logical system for Client
    Partn.Type       LS                    Logical system
    Function                                  BLANKKKKKKKKKK
    Port                            SAPDPI
    Partner number             CLNTSAMPLE
    Partn.Type                      LS         Logical system
    Partner Role                   BLANKKKKKKKKKK
    My configurations are Like this :----
    On ECC  Side  MY SID is DEC
    On ECC side I have two logical system in CLNTDPI100 for PI
                             CLNTDEC110 for ECC.
    I have Partner profile on ECC system on CLNTDPI100 logical system    - we20
    Added message type in inbound side of partner Profile (INVOIC-INVOIC02)
    ON SAP PI/ XI System  MY SID is DPI
    IDX 1 has Port name SAPDEC
    On Message mapping EDI_DC40 is mapping with constants with below given value
    <INVOIC02>
       <IDOC BEGIN="">
          <EDI_DC40 SEGMENT="">
             <TABNAM> </TABNAM>
             <DIRECT>2</DIRECT>
             <IDOCTYP> </IDOCTYP>
             <MESTYP>INVOIC</MESTYP>
             <SNDPOR>SAPDPI</SNDPOR>
             <SNDPRT>LS</SNDPRT>
             <SNDPRN>CLNTDPI100</SNDPRN>
             <RCVPOR>SAPDEC</RCVPOR>
             <RCVPRT>LS</RCVPRT>
             <RCVPRN>CLNTDEC110</RCVPRN>
          </EDI_DC40>
    Regards
    PS

    Check the following :
    in We 02 which  partner number is displayed just in the posted IDOC -> 2nd coloum in the IDOC list .and verify if the
    same you have in Partner profile. Actually this details comes from  ECC business system's logical system name which you give in SLD.
    in we 19  - take the error iDOC numner and  open the IDOC ->click on the first line -> check entries as you mentioned
    above  sender port should be PI port not empty.you need to check the partner profiles properly
    follow these steps
    1. create a RFC destination of tyoe H for Pi system- 2. create a Port  and assigen the RFC destination to it
    3 create logical system for PI BD54 PICLNT001 say , 4 with the same name create a partner profile in We20
        in parter profile  maintain the  inbbound message parameters  and add the PI port as receiver port in it .Give the basic type also .
    now
    for sender details  in ur case PI : u have  port (defined in PI IDX1),patner number (LS defined in ECC PICLNT001), parter type LS.
    for  receiver  you have port defined (as above), partner number the logical system for ECC system.
    in we 19 ,, edit the control record as above and  go to the tab inbound processing and test the internal posting
    it should work fine. in the adapte specific attribuet for receiver ECC system , maitain the same LS name , if any wrong entry is
    there then change the LS in sld to poing to correct LS/
    refer this
    http://www.riyaz.net/blog/xipi-settings-in-r3-partner-system-to-receive-idocs/technology/sap/26/
    Regards,
    Srinivas

  • Why T-RFC Port canu2019t handle Partner Profile Segment Release Version.

    Can TRFC Port handle the segment release of each of the segment if configured in Partner Profile.
    As per sap, in Partner Profile,  if we maintain the two field "Seg. Release in IDoc Type"  and "Segment Application release" to a SAP Release lower than the current release version then all the segment populated by the IDoc adapter should be populated as per the lower release structure.
    For test Purpose I have created two IDoc using File Port and TRFC port and for both of then I have maintained the Partner Profile Fields  "Seg Release in IDoc Type" and "Segment Application Release" as 46C although the latest release is 701. 
    In the IDoc there is a custom segment ZE1PMX with two Version Release 46C & 701. 46C is having 7 Fields and 701 is having 9 fields.
    Test using TRFC Port: Using TRFC port the IDoc that is getting generated are not having the segment structure of release 46C instead of that it is taking the segment structure of latest release 701 which is having 9 fields.
    Test using File Port: Using File port the IDoc that is getting generated are having the segment structure of release 46C instead of latest release 701 which is having 7 fields which is desirable.
    I have also done these testing in other SAP release like 700 and found that while saving the partner profile with a lower  segment release number it throws an warning message as "Segment definitions missing for release 620/620" and IDocs are not getting generated with a error status Code 2 "Segment E1BPMEPOITEM1 is unknown in Release 620 /". But from release 701 sap allows us to save the Partner Profile without warning and also creates the IDoc without error but the segments takes the latest release structure instead of the release maintained in the Partner Profile.
    If any one has already done some investigation on this issue please let me know why there is a difference in TRFC Port and File Port. Is there any other configuration that is missing for T-RFC Port.

    Hi Dennis
    This forum is focused on [SAP NetWeaver Gateway|http://www.sdn.sap.com/irj/sdn/gateway], i.e. the (relatively) new OData/REST-orientated mechanism to expose ERP data and functions.
    You're talking about the ('classic') Gateway i.e. the service that runs on port 33<SYSNR>. As a result, you are better off posting in the forum that covers that Gateway, i.e. [Application Server Infrastructure|SAP NetWeaver Application Server;
    The names do make it confusing, for sure.
    Good luck!
    dj

Maybe you are looking for

  • Binary to XMl Conversion

    Hi All, I am trying to convert data from internal table to Binary and then taking the same in the XML format for Display. Steps 1 : from internal table to Binary conversion. create & set encoding lo_encoding = lo_ixml->create_encoding(               

  • I seem stuck in a loop of incompetence

    Hi, I recently rang to cancel my BT TV service, I was talked into staying on a reduced £2 (reduced from £5) a month 'tv essential' package, and duly received an email showing my reduction and that my total would be £2 for 12 months. I then received m

  • Itunes crashed while updating.

    Itunes crashed while updating. Now Im getting error 6 nonstop. Can this be fixed? So far I have found no answers. No backups of the phone exist according to itunes.

  • Export meet ora-3113 error!

    In my database there are two scheama t1 ,t2. When I use the command 'export' to export the data in 'USER' mode,one of the scheama t1 meet the oracle error ORA-3113,but the other t2 is ok! the error occured when t1's tables are exported and would be e

  • Need to setup filesharing for 15 macs / photo retouching

    I'm currently using a 4TB Buffalo Terastation NAS, with all users connected by ethernet. What's the best way to improve overall speed performance? Users need to work directly off the shared drive. We are a small retouching studio. The current setup i