EDI Settings

Hi All
can anyone tell me how EDI settings are done for Purchase orders and intercompany billing docs.
Transaction codes would be of much help step by step.i think i know there are four Tcodes. WEL1 for logical address , WE20 for partner profiles and OBCA for assigning invoice to company code.
Can anyone correct me if i am wrong..

Hi,
For configuring of EDI for Invoice, you have to do following things :
1. Use Outbound IDOC type u2013 INVOIC01 (Message type u2013 INVOIC)
2. Maintain Condition Record for Billing Output (EDI)
Transaction Code : VV31 / VV32 / VV33
Output Type : RD00
3. Port in IDOC processing
Transaction Code : WE21
Port Type - > File Port : For eg . - EDIFACT
Maintain all the relevant field like physical path for directory, Functional module for file name.
4. Create Partner Profile
Transaction Code u2013 WE20
Select Partner type KU (Customer) and maintain outbound parameters for Outbound IDoc - INCOIC01
Some Important Transaction Codes for EDI Configuration which you have to know.
WE63 - Documentation IDOC Type
WE46 - IDOC Administration
WE16 - Trigger Inbound processing
WE19 - Test Tools for IDOC Processing
WE02 u2013 IDOC Status
WE05 u2013 IDOC Status
We07 u2013 IDOC Statistic
Hope you can configure now.
Cheers.....
Imran

Similar Messages

  • EDI settings for Purchase scheduling agreement

    Hello,
    We are having one new requirement,
    Purchase scheduling agreement created for foriegn or local vendor, the Schedule lines are created or release by MRP run.
    After MRP run the schedule lines are going to create , then vendor can get the message  though IDOC,
    How can we customise the ALE and Idoc settings for above said scenario.

    Hi Mahesh
    After schedule lines are created for SA we have provision of schedule line release transfer to Vendor , please check whether output determination is feasible with medium as Idoc
    Please check
    Kishor

  • Invoice EDI error : EDI: Partner profile inbound not available

    Hi  EDI experts ,
    We are connecting our SAP ECC 6 ( Ehp 4) system to 3rd party system Mincom via SAP PI, to send PO Creation message (Outbound) and receive Vendor Invoice message( inbound).  We already done all the settings..Output determination procedure, Partner Profile ( WE20) , Port creation , Condition Records, EDI settings in SPRO for invoice..etc as below:
    Logical system ( BD54)
    ECC system - EDACLNT112,
    PI systems u2013 IDACLNT210
    Third party u2013 LSMINCOM
    Port ( WE21)
    IDACLNT510 : For PI with RFC destination IDACLNT510
    Partner ( WE20)
    LSMINCOM :  (Partn.Type LS)
    Outbound parmtrs.- Partner Role- LS, Message : ORDERS , Port - IDACLNT510
    Inbound parmtrs.- Partner Role- LS, Message : INVOIC , Message Variant- MM, Process code u2013 INVL, Trigger immediately (Process code INVL have  Identification - IDOC_INPUT_INVOIC_MRM, Option ALE u2013 Processing with ALE services , Processing type- processing by functional module)
    Here PO Creation is working fine . IDoC of PO outbound message have below details :
    Recipient information:
    Port :     IDACLNT510 (Logical system & Port created in WE21 )
    Partner Number :  LSMINCOM   ( Logical system and Partner created in WE20)
    Partn.Type :  LS        
    Function :  LS     
    Sender information:
    Port :  SAPEDA ( donu2019t know how it created..but in WE21..it is not there)
    Partner number:   EDACLNT112 ( Logical system and Partner created in WE20)
    Partn.Type :  LS        
    Partner Role :Blank
    Just started testing, our PI team is sending the IDoC, with wrong information on partner & other data, so inbound IDoC failing with error u201CEDI: Partner profile not availableu201D. Oaky. I reprocessed these failed IDoCs by changing Partner data just opposite (i.e. Sender info as Recipient info & vice versa) to successful PO Creation O/B message in WE19 in EDIDC and when I click on u201CStandard Inboundu201D, then another window open giving error message u201CPartner profile not maintainedu201D and creates new IDoC with status 56
    EDI: Partner profile inbound not availableMessage no. E0337
    Diagnosis
    An inbound partner profile could not be found with the following key:
    /LSMINCOM/LS//INVOIC///X/
    This involves the key fields of table EDP21:
    -SNDPRN  partner number of sender
    -SNDPRT  partner type of sender
    -SNDPFC  partner function of sender
    -MESTYP  logical message type
    -MESCOD  logical message code
    -MESFCT  logical message function
    -TEST    test flag
    Procedure
    Please check the inbound partner profiles.
    Execute function
    I am not getting exactly what inbound partner profile could not be found or what is the problem here . Can anyone suggest me what should be the problem and solution on it ?
    Thanks
    NAP

    Narendra,
    Please advice what was the solution.

  • Error:maintain out going EDI Connection for Partner 1000

    Dear Gurus,
    I have output master record for vendor 1000 and i have done edi settings namely fileport, partner prifile. My problem is
    1While creating PO, the settings are not reflected ( i checked them in Path Goto->mesages.) When i try to give them manually the erros says"MAINTAIN OUTGOING EDICONNECTION FOR PARTNER 1000"
    Please let me know how to correct it.
    Regards
    Rao

    HI Mano,
    Make sure to create entries for output control as well as for outbound parameters.
    XXXX is defined in the partner profile by WE20.
    To this XXXX partner, there are two setup are needed to solve the issue in WE20:
    1 . Partner Role is required ( like LS for Logical system).
    2. in Message Control tab, an Apllication/Message Type/Process code record is required as well. The message Type is actually the output type.
    Please check these and post if it is not resolved.
    Regards,
    Madhu.
    Edited by: madhurao123 on Jun 24, 2011 8:47 AM

  • IDOC EDI mapping ..

    hi,
    Please let me know if my understanding is correct. In SAP EDI setup two people involved, ABAP programmer who customzes the IDOCS, sets up the EDI setup on SAP side like number ranges, partner profiles, condition records, message control etc and monitors the IDOC status till it is transmitted to the EDI subsystem and also the IDOCs received at SAP end.
    The other person is an EDI specialist who will map the IDOCs to the EDI doc set based on trading partner requirements in the EDI subsystem.
    So the ABAP deveoper need not know anything about the mapping done at EDI subsystem ?? His job is only at the SAP end ?? Am I right ??
    thanks
    Edited by: sdnuser1 sdnsurname on Mar 20, 2008 6:03 AM

    Hi,
    Ur assumptions are correct up to some extent...
    What will happen SAP EDI implementation proejcts is most of the times it is the SAP technical people responsibility to do the EDI mapping also.
    So an ABAPer with EDI knowledege(ABAP/EDI consultant) will take care of SAP EDI settings at SAP side and he/she will develop the mapping document and hand over the same to EDI sybsystem provider.
    EDI subsystem people will feed the mapping instructions into EDI subsystem based on ur mapping document.Core EDI people will not understand the SAP terminology and as ABAP/EDI consultant will take of both settings.For an ABAP/EDI consultant also will not be given full access of EDI subsystem and u will only hand over the mapping docuemnt(IDOC segments to EDI standards mapping ) and they will feed the instructiona and get back 2 u for any doubts..
    Hope this help.Let me know if u need any help for further understanding..
    Rward if helpfulll
    ramesh

  • EDI message is not sending to the third party for one particular SA

    DearAll,
                   We have the scenario to send the schedule lines to the third party system. for one particular schedule agreement schedule lines not sending to the third party system.
    while processing the messgae it is giving the error as "Message XEDI already processed on 20110317 070042"
    What could be the reason?.. we have checked all the EDI settings maintained for this supplier. some two weeks back there is no problem now only getting this message.
    how to resolve this?..
    Thanks in Advance
    Ananth.

    Hi Hareesh,
    Thanks a lot for the help. I have tried with removing the xml namespace, still the same result. I believe, the problem is with MTs tag in response message structure, bank xml data is trying to map with the response structure in PI, but when its finding the MTs tag I believe then its not mapping, and directly its passing the response in SXMB_MONI without any mapping.
    My question is how can I define my response structure without the MTs tagm, I mean same as what I am receiving from bank.
    Also I tried with without any mapping in response structure, I mean I used only one Message type for "response from bank" to "response to ECC" , without xml namespace, in this case I am able to receive the response in ECC, but there is exception called "PARSE_APPLICATION_DATA Error during XML => ABAP
    conversion: Response Message; CX_ST_MATCH_ELEMENT in " while receiving response, and when I go and see the logs, it says "System expected element 'MT_Response_MT940_Test'" , as its try to match with the defined structure in PI.
    Please experts help me, so my question is how can I avoid the MTs tag in my response structure, I just want to define my response structure in PI same as bank is sending me the data in xml tag, without any MTs tag.
    Thanks,
    Farhan

  • 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.

  • Post GL Accounts based on valauation class in EDI Postings

    Hi,
    We have a business requirement in intercompany billing postings.  At the time of posting the account receivable posting through intercompany billing, system also post account payable posing based on the EDI settings.  However standard EDI settings for determine GL Account is based on the vendor and company code not on the basis of valuation class.  Hence, we need to determine the account payable gl accounts based on valuation class instead of GL Accounts assigned in EDI.
    For that we through of using the Enhancement FEDI0001 and userexit EXIT_SAPLIEDI_001. However this exit is not trigerring while inbound idoc is processed.
    Kindly advice how we need to process and whether we are using the right userexit or not.
    Best Regards.,
    Goutham

    not answered

  • Outbound EDI 860/Inbound EDI 865 Integrated to JDE 9

    Has anyone successfully integrated an outbound EDI 860 and an inbound EDI 865 into JDE 9?

    Hi,
    I think Order05 should work for you. Let me try to answer your questions
    1) which IDOC message type should i use for this transaction, to send an 865 ?
    A: ORDERS. Basic type should be ORDERS05
    2) What program and Form routine should i use to send an 865 , while configuring the output type in V/30 ?
    A: RSNASTED. Form routine: EDI_PROCESSING which is pretty standard. You can use BA00 output type which is standard again.
    3) Please advice me the SAP setting we need to do for an 865 (order change Ack) .
    A:  i. You should have the EDI settings done by your Basis team. (Else Idocs will not generate)
         ii. You should create a partner profile in WE20 for KU customer, outbound.
        iii. In the Outbound options mention the port and other stuff. Maintain the message control. Note that you put in BA00 there in  the message type and put the right process code (Should be SD01).
    I think these are the only things. Try and this should work for you.
    Regards,
    Mukund S

  • EDI 865,order change acknowlegment via edi

    HI Guru's.
    I hope you will help me with your expertise, i have a requirement with my client to have an EDI 865(outbound) message without having an 860 (inbound). Eg, customer will not sent an 860 message, and requesting an 865 , when  ever there is a change in the sales order for some fields, we need to send an 865 EDI message.
    My Questions:
    1) which IDOC message type should i use for this transaction, to send an 865 ?
    2)What program and Form routine should i use to send an 865 , while configuring the output type in V/30 ?
    3) Please advice me the SAP setting we need to do for an 865 (order change Ack) .
    Your input is highly appreciated,
    << Moderator message - Please do not promise points >>
    Thank you all for reading this Post.
    Edited by: Rob Burbank on Feb 1, 2011 5:41 PM

    Hi,
    I think Order05 should work for you. Let me try to answer your questions
    1) which IDOC message type should i use for this transaction, to send an 865 ?
    A: ORDERS. Basic type should be ORDERS05
    2) What program and Form routine should i use to send an 865 , while configuring the output type in V/30 ?
    A: RSNASTED. Form routine: EDI_PROCESSING which is pretty standard. You can use BA00 output type which is standard again.
    3) Please advice me the SAP setting we need to do for an 865 (order change Ack) .
    A:  i. You should have the EDI settings done by your Basis team. (Else Idocs will not generate)
         ii. You should create a partner profile in WE20 for KU customer, outbound.
        iii. In the Outbound options mention the port and other stuff. Maintain the message control. Note that you put in BA00 there in  the message type and put the right process code (Should be SD01).
    I think these are the only things. Try and this should work for you.
    Regards,
    Mukund S

  • Error 'No tax code found for difference' in Posting Vendor Invoice IDOC

    Hi All,
    I am getting error message 'No tax code found for difference' while posting Vendor Invoice IDOC into SAP. IDOC type is INVOIC02. There is no difference in PO price, Invoice price and even Standard price. then why this  error message? Other Vendor EDI settings are done ( OBCA, OBCD, OBCE etc). Is there any thing specific to be done in the config for this error?
    IDOC has PO  as reference document.
    I looked into several threads in SDN forum but could not find proper solution
    Can any ine help me with this issue?
    Thanks in advance
    Hari

    Hi
    You might be  missing the tax code for uploding through IDOC
    so you can use the t.code we02 and give the doc and find the error
    go to the WE19 to edit the tax  code
    and USE the t.code  BD87  to select the doc and process it
    thanks
    Madhu

  • Error while creating IDOC from payment run

    Dear All,
    I 've alredy done all EDI settings for creating IDOC from payment run. But system in not generating IDOC as end with a result as "House bank is not designated as a EDI Partner'.
    Please suggest how to define house bank as a EDI partner.
    Regards,
    Subhash

    From We20 u have to create the partner profile for the bank u r using in ur transaction. In we20 select the partner type B (Bank) and as Partner no give ur bank numbrer.
    Regards,
    Joy.

  • Cross-Company Stock Transfer with Delivery and Billing

    Hello Fellow Experts and Friends,
    I have a situation at a client in California. The client does Make-to-Order sales. The only materials kept in inventory are raw materials and NREs. This client has plants in several countries around the world but only two are on SAP. The current version is 4.6C.
    The scenario goes like this. The plant in China (CC: 2020, Plnt: 0020) wants to order raw materials from the US plant (CC: 1010, Plnt: 0010). If the US plant does not have enough stock in inventory, an order needs to be placed with a local vendor. When all materials a re available to ship,we need to deliver to and invoice the China plant. Additionally, shipment notification needs to be sent to the plant in China.
    IWould someone please be so kind as to helpme with a "Best Practice" process flow for Cross-Company STO with Delivery and Billing? I also need guidlines for customizing the process in the IMG. This process must include issuing a PO to a local vendor for ordering additional inventory. For the shipment notification, I was thinking of an EDI Advance Shipment Notice if the receiving plant uses EDI. I need a different option, If the receiving palnt does not use EDI.
    I am open to your suggestions.
    Thanks,
    AJ
    Edited by: Arthur Hawley on Sep 8, 2009 10:56 PM
    Edited by: Arthur Hawley on Sep 11, 2009 4:46 PM

    Arthur,
    Once this is correctly set up it works very, very well.  And the cross-company supply scenario is actually fairly simple, streamlined and automated.  However, this is NOT such a simple process to set up.
    True cross-company supply, all the way through, requires a LOT of configuration which ties in SD, MM, FI, and EDI.  It uses "wrap-around" IDocs to do some of the cross-posting in other company codes.  There is also the issue of Intercompany markups, as well as Intercompany eliminations.
    There are LOTS of folks who do the painful process of the FULL Order to Cash in one company code, and the full Purchase to Pay in the other.  But this is NOT the right solution and requires almost twice as much transaction processing.
    Just for the Intercompany setup, start to finish, I've been working on a "cookbook" to set up all of the modules for almost 10 years now.  I've done it several times, at several companies and it works very well once it is all in place.  However, that cookbook document is about 100 pages long (config settings, IMG settings, master data requirements, EDI settings, etc.).
    Also, in your scenario you are talking about multi-sourcing parts from other locations.  All of the related MRP settings are a separate setup issue.
    What you are asking is WAYYYYyyy beyond the scope of forum posting.  So if your company or client could use some help, please feel free to contact me.
    Bill Wood - President
    R3Now Consulting
    http://www.r3now.com SAP thought leadership!
    Platinum SAP Solutions
    (704) 905 - 5175
    http://www.linkedin.com/in/billwood

  • STO Outbound delivery issue

    Hi All,
    I've a intercompany customer (say ICABCD) which has Ship-to Party maintained as 12345678 (not same as Sold-to Party) in Customer master. Now when I create a I/C PO to procure goods for ICABCD and create delivery (outbound), it sets Ship-to Party in delivery as ICABCD, not 12345678. Partner determination at delivery level is perfectly fine and has no issues at all.
    As a result when I create a I/C billing document and Commercial Invoice subsequently, it gives the Ship-to Party address as ICABCD address in Commercial Invoice since it is taking VBPA-KUNNR with PARVW=SH by passing Billing document number. I know the workaround could be referring KNVP-KUNNR, PARVW=SH (and VKORG).
    But at the first place, why it is not determining the correct Ship-to Party in Delivery? Is there a solution for this? Is this the standard behavior?
    Awaiting your replies.
    Regards
    Samier Danish

    there is no extra ship-to party.
    the whole logistics customizing is between receiving plant (which is ship-to ) and sending plant (vendor).
    the sold-to does not really play any role, except it is identical with the bill-to party, this one is then mentioned in the EDI settings for invoice exchange.

  • Partner Profile and its configuration.

    Hi all,
    I am creating an SD IDoc using EDI and send it between two servers.
    I need to know what is a partner profile and why should we create it.
    what are the steps to be followed in maintaining a partner profile and its configuration.
    Any pointers will be highly apppreciated.
    Thanks in advance,
    Regards,
    Jose
    Edited by: Jose Anthony Reddy on Dec 17, 2007 11:23 PM

    Hi Jose,
    Below is a material you can go through .
    Creating an Outbound Partner Profile
    Here you must enter the data manually. Alternatively, you can also transfer the default values from Customizing.
    If you are not yet on the change screen of your desired partner, choose SAP Menu ® Tools ® IDoc Interface/ALE ® Administration ® Runtime Settings ® Partner Agreement (WE20).
    1. Position the mouse on your partner in the required partner type node. Choose in the Outbound Parameter table.
    Key Fields
    2. You have already determined partner number and partner type in general partner processing. The partner function from the master data defines the addressee, that is, it is used for further classification purposes. If you have selected outbound processing under Message Control (MC), the function must be identical to the corresponding Message Control field. Otherwise, it is optional.
    Partner A (customer 1110) wants to order a material from partner B (vendor 1014). Partner B is of the partner type “LI” (vendor) and must choose the Message Control value “VD” (vendor) as the partner function because orders must always be processed using Message Control.
    3. Specify the business process with the “logical” message, within which the IDoc type is used. The logical message is described by three parameters: The message type is based on EDIFACT message types: For example, a purchase order is of type “ORDERS”. You can further divide the message type with the optional fields message code and message function.
    4. Configure the test indicator if you want to send the message as a test.
    Message, partner and test indicator are the seven key fields of the outbound partner profiles (the client comes in addition to these). Also see the graphic at the end of this section.
    Other Fields
    5. In the Outbound options tab page, you can determine whether IDocs are forwarded immediately to the receiving system. You should ensure that your entries are compatible with the Message Control priorities, if you have chosen outbound processing under Message Control. A list of recommended combinations is provided in the section Outbound Processing Under MC: Procedure.
    6. You have already defined the Recipient port in Port definition.
    7. If a port of type TRFC is used, the Queue Processing field is visible. You can use the indicator to specify whether IDocs are to be sent with qRFC. This sending technique is only possible for recipient SAP systems as of SAP Web AS 6.20.
    You should only set this flag if it is really necessary that the IDocs sent are received in the receiving system in the same sequence as they were sent by the sender system. Queuing can cause posting delays in the receiving system, because an IDoc in the queue cannot be posted. In this case, the following IDocs in the queue cannot be posted until the error is resolved.
    8. If you have set the Queue Processing indicator, the Rule Name field, which you must then also maintain, appears as well. The rule name defines the rules for queue names. You can specify these rules in the transaction qRFC IDoc Queue Name Rules (WE85).
    9. Specify the IDoc type as the Basic type with or without extension. If you want to use a view of your IDoc type (for example, to improve the performance), specify this here.
    The figure below shows the m-to-n relationship between logical messages (business meaning) and IDoc types (technical format). Message 1, for example, is always assigned to one IDoc type, while message 3 is assigned to two IDoc types. IDoc type 2, in turn, is also assigned to 2 logical messages.
    10. The segment release specifies the release from which the segment definitions (not the IDoc type definition) originates. We recommend that you leave this field blank so that the most recent segment definition is used.
    11. You can propose an EDI standard, version and EDI message type for the receiving system in the tab page EDI Standard. Most subsystems, however, should be able to determine these EDI settings themselves (from the logical message).
    12. You can define permitted agents for cases in which exceptions occur. This entry overrides the entry in the general partner profiles. Depending on the message, therefore, the exception can be handled by different agents of the same partner.
    13. You can specify whether syntax errors are to be ignored or are to lead to a processing error (Cancel Processing flag under syntax check in the tab page outbound options). For more information about exception handling and permitted agents, refer to the following section: Exception Handling
    14. If your hardware supports it, create partner and message specific telephony data for outbound IDocs. For more information, see General Partner Profile.
    Graphic: Outbound partner profile fields (general)
    Key fields are shown in gray. The values for partner, message and test indicator (and client) therefore provide a unique ID for the IDoc type in outbound processing.
    Regards,
    Praveen

Maybe you are looking for