IDOC-XI-IDOC:CRM-PI-R/3(Both Idoc are same nameProblem)

Hi all
I have a scenario in which CRM triggers and IDOC via transaction WE19 which goes to PI and then to R/3.
My problem is that i have to map IDOCs from CRM and R/3  in XI  and both have the same name
1. In CRM ZDOC.ZDOC01
2. In R/3 ZDOC.ZDOC01
IF i import them under one software component then it overwrites the former one because of the same name. To solve this I made two diff IDOCs in CRm and R/3 respectively
1. ZWDOC.ZWDOC01
2. ZDOC.ZDOC01
but when following the link I m getting confused as to what i should enter in Configuration -> Receiver determination -> Interface Determination.
Also I am not sure what all settings are needed.
Please solve my problem.
Regards
Naina

Hi
What i did is changed the name of IDOC in CRM and then i am able to import both from CRM and r/3.
Actually i m not sure about all the settings....is there any link that you can suggest or any of you have done this before.
Also if i go and check in sld ....My crm business system is connected to to client 100 whereas i need to send IDOCs from Crm client 120 to PI to R/3 120.
Help me understanding the issue.
Naina

Similar Messages

  • Both terms are same or different

    Hi gurus
    Is Intra company sales transactions and  stock transfer order both  terms are same.  Both the business scenario is the same or differnt i would like to know  about this
    Points will be rewarded.
    thanks & Regards
    rack29

    First basic difference between both the process is.
    Inter company Sales: Normally this a sales process
    Inter company Stock transfer is a MM Process.
    In Inter company sales you will sell to your customer to different plant of different company code .
    Example: If customer will order goods to Sales organization 1000 which is assigned to company code 1000 and plant 1000. In case if the plant 1000 does not have stock  then he will create sales order in sales area of company code 1000 and in sales order he line item we have to change plant manually from where the delivery will happen in case if the delivery is happening from plant 2000 which is assigned to company code 2000 then in sales order line item the plant should be 2000.
    And the delivery will be happened from plant 2000. And sales organization 1000 will bill to his customer and company code 2000 will bill to company code 1000 Billing type is IV.
    Note: Material should be available in both the plants.
    This is Inter company sales process.
    Inter company Stock transfer
    If plant 1000 want to goods from plant 2000 then plant 1000 will raise Purchase order ME21n  and deliver will be happen using transaction code VL10b and invoice will happen using billing type IV then MIRO will happen.
    This is Inter Company stock transfer.
    Thanks,
    T.Nishanth

  • Differences in LC2 and LC3 even both currencies are same

    Hi Experts,
    I hope everyone is doing well. I have an issue with Local Currency2 and Local Currency3.
    Here my issue is when I post an invoice using Transaction Code MIRO the amount in Local Currency2 (USD) and Local Currency3 (USD) is different even though both the currencies are USD. Please find the below example.
    Pstg Key  Account   A/c Short Text      Amt in L Cur  L Curr         LC2 Amnt                  LC3 Amnt  
         31        234567    Venodor Account         9.137,26-    AUD       6.708,58- (USD)      6.708,58 (USD)
         86        568568     Purchase Price Var     8.306,60     AUD             0,00  (USD)      6.098,71 (USD)
         83        556321     Ex Rate Var Settle            0,00     AUD       6.098,71  (USD)           0,00  (USD)
         40        586974     VAT Asse                     830,66     AUD          609,87  (USD)        609,87 (USD)
    Local Currency : AUD,   Local Currency2: USD,   Local Currency3: USD
    In the above stated example there is no problem for the accounts 234567 and 586974. But for the accounts 568568 and 556321 the amounts are different. There should not be any exchange rate difference postings i.e to account 556321. I am not able to find out how it is posting to exchange rate variance settlement account (556321). Please help me what could be the reason for these differences.
    Thanks and Regards,
    Havina

    Hi Deepak,
    The settings in OB22 are as below:-
    1st Local Currency:
    Crcy type  10    Company code currency                        Currency   AUD
    Valuation  0     Legal Valuation
    ExRateType M     Standard translation at average rate
    Srce curr. 1     Translation taking transaction currency as a basis
    TrsDte typ 3     Translation date
    2nd Local Currency:
    Crcy type  30    Group currency                               Currency   USD
    Valuation  1     Group Valuation
    ExRateType M     Standard translation at average rate
    Srce curr. 2     Translation taking first local currency as a basis
    TrsDte typ 2     Posting date
    3rd Local Currency:
    Crcy type  30    Group currency                               Currency   USD
    Valuation  0     Legal Valuation
    ExRateType M     Standard translation at average rate
    Srce curr. 2     Translation taking first local currency as a basis
    TrsDte typ 2     Posting date
    And the postings are as below:
                                            AUD (LC1)      USD(LC2)        USD(LC3)
    Purchase Price Var           8.306,60             0,00             6.098,71
    Ex Rate Var Settle               0,00            6.098,71             0,00
    And these differences are posting only for Purchase Price Variance account and Ex Rate Var Settlement account as shown above.
    Please suggest what could be the reason for this.
    Regards,
    Havina

  • ALE VA01 IDOCs are sent two times ?

    My ALE is working well, but for eacher sales order created, Two Idocs are send (Two different idoc number but the same sales order)!
    I use message controle and a partner profile Ku ans LS.
    So where can I check where is this double ?
    Transaction ? Tables ? Spro?
    Best regards
    Henri

    Hi Henri,
    Why do you need to have two partner profile KU and LS?
    Unless you want to send to different target systems. For example, KU is for customer 'ABC' and LS for CRM system.
    If you need only to send one target system then use only partner profile and delete the other one.
    Please ensure the two IDoc generated are having two different recipient (KU and LS) in IDoc control.
    If both IDocs have same recipient then you may need to check the ALE and IDoc configuration again.
    Please check NAST table for initial investigation.
    Hope this will help.
    and don't forget to reward points if helpful as a way to say thanks.
    Regards,
    Ferry Lianto

  • Two idocs with same idoc number in idx5

    We are using an idoc to file scenario where idocs are bundled using bpm and posted to ftp. here the issue is we are getting two idocs with same idoc number in idx5. due to which the file in ftp is getting overwritten.
    Could anyone suggest me what to do in this regard.

    Hi,
    >>>check your sender system is sending same IDoc twice ?
    if you send the same IDOC twice they both get different numbers as IDOC number is taken from the IDOC num range
    unless you're able to send the same IDOC twice with the same IDOC num somehow
    Regards,
    Michal Krawczyk

  • Creation of SO from PO through Idocs in Same client

    Hi frnds,
         Can we create SO from PO through IDOC's in the same client with different company codes.
    Ex: PO created in 100 client in company code AB00. i have to create SO in 100 client in company code AB01.
    Any suggestion on this is highly appreciated. Please provide the steps and idocs or let me know the other approach.

    for posting the IDOC to same system
    use this logic
    The steps to send and receive an IDoc in the same system are as follows:
    u2022     Create a Dummy Logical System.
         Goto T-Code SALE-> sending and Receiving Systems -> Logical Systems -> New entries. Enter SYSID_CLNT, but this one is Dummy so use the first two characters of the SYSID and prefix 'D' then underscore and then the Client number.
    E.g., If ERP_100 is the logical system of the R/3, then create ERD_100 as the dummy system.
    u2022     Create Port for the Original System, (ERP_100)
         Goto WE21 and select Transactional Port and press the Create button. Name the Port as "SAP" concatenated with the SYSID in our example it would be SAPERP Select the appropriate version and enter the RFC destination of the system that you are working on in this case it will be 'ERP'.
    u2022     Create Partner Profile in partner type LS:
         Receiver Side (Outbound to): In Partner type LS name ERD_100create the Outbound Parameters, give the Message type, Receiver Port same as the port we created in step 2. Enter the Basic type.
         Sender Side (Inbound from): In partner type LS name ERP_100 create the Inbound Parameters, give the appropriate message type and the process code.
    u2022     Now create the stand alone program to send the IDoc:
         The program will at some point calls the MASTER_IDOC_DISTRIBUTE function module. When you pass the EDIDC structure it will be populated as follows:
    i_edidc-mestyp = message type.
    i_edidc-idoctp = basic type.
    i_edidc-rcvprt = 'LS'.
    CONCATENATE 'SAP' sy-sysid INTO l_port.
    i_edidc-RCVPOR = l_port.
    i_edidc-rcvprn = 'ERD_000'.
    CONCATENATE sy-sysid '_' sy-mandt INTO l_sndprn.
    i_edidc-SNDPRN = l_sndprn.
    i_edidc-sndprt = 'LS'.
    i_edidc-sndpor = l_port.
    u2022     Observe that the Sender port and the receiver port is the same, this does the trick. The outbound Idoc is sent on the port SAPERP with the Sender as ERP_100 and receiver as ERD_100 and then the Inbound IDoc is also sent to the same port SAPERP with the Sender as ERP_100 and receiver as ERD_10.
    this is the method for creating logical system and setting
    and use the respective function module and mesg type for posting it.
    cheers
    s.janagar
    Edited by: Janagar Sundaramoorthy Nadar on Apr 29, 2009 6:32 AM

  • IDocs are not transfering to XI

    Hi,
    When we create Shopping cart, in the back PO will create and it woould convert to IDoc and send to XI. But PO's are creating, IDocs are not reaching to XI, please let me know what would be the issue.
    Thanks

    HI,
    Try this URL , i hope it will help u ,
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a?quicklink=index&overridelayout=true
    Regards,
    S.Saravana

  • Two idocs are created for one output message type

    hi all,
    we are communicating our sap idocs to external system using ALE.It is working smoothly.
    Our problem raises here,
    .idocs are creating at the time of output type attachment for purchase orders.But rarely,two idocs are creating for one message type.It means two idocs are created for same Purchase order.It makes complications for the external system.
    anyone can help me pls?
    thnks in advance..........

    thanks jurgen for ur reply,
    jurgen, the second idoc is not an "ORDCHG",It is the replica of first idoc.This one has also "ORDERS" message type.The only difference between these idocs are the time.It means the difference between the time field segments of these idocs have only three(3)seconds difference.We think that its from the system error.If it is not from the system error pls give me the explanation.
    thanks in advance.......

  • Message types not in BD64 and WE20,but idocs are passing

    Hello ,
    we are facing a strange scenario.
    between two partner systems A and B, 4 message types are maintained.
    Idocs exchange to and fro.
    but in system B, few idocs are visible which are having sender as system A.
    but if i check in system A, these idocs are not sent at all.
    this emssage type is not maintained in either of the partner profiles as well.
    can anyone throw light what is happening ?
    Regards,
    Chaitanya

    solved by restarting

  • Idocs are failing

    Hi,
    We have a Z program which creates Inbound idocs by processing the files at the application layer. Once the idoc is procesed, based on our business requirement we split the parent idoc into more than one idoc with different message type and process them once again. Now we are seeing a new problem, the child idocs are not getting processed at all and simply moving into the status 51 with with a special message "Application log is already open and cannot be reopened." or "Period indicator T is not defined". These messages are not maintained by us as we maintain some messages to update the application log.  There is no instance where we have failed to close the application log.  Strange things is idocs gets posted when I manually process it by using program RBDPROCESS. They either get posted or will remain in status 51 - with valid message. 
    I have checked all the settings for ALE and Idocs. Everything is working fine. Actually we have three testing sytems, the same setup works fine on one system but is failing on the other two boxes.
    Please help me to resolve this.
    Thank you,
    Ganesh Prasanna.T

    hi ganesh,
    i believe u split ur idocs based on some conditions. plz chk if u r meeting all the conditions.
    also ask basis team if they have any option 2 clear the buffer like if any.
    am not very much sure.
    just try n chk out if helpful.
    reward if helpful
    kiran

  • EREC: Multipal IDOC are getting created in receiver system for one IDOC

    Hello Experts,
    I ran in to one wearied issue in IDOC creation in Receiver system. I am running PFAL in sender system for only Person but 10 IDOC are getting created in receiver system. I don't know why is this happening.
    This issue started popping up after we ran RBDAPP01-Inbound Processing of IDocs Ready for Transfer. We ran this to change IDOC to 53 status. Now I don't know what went wrong but Perner distribution is behaving
    Appreciate your help.
    Regards,
    Krishna Bidwai
    Losangeles USA.
    818 527 0204.

    Yes, employee is getting created after adding 0003 into the filter, but can u please answer my another question, i.e. PERNR in sender and receiver system should be same.
    So in Receiver system (ECC) do i need to maintain external number range for PERNR?
    Thanks

  • Idoc are posting to ECC with Status 64

    Hi All,
    We are receiving IDOC with status 64 from PI.
    We used tried by changing the options in partner profiles
    --> Trigger by Background program
    The inbound IDoc is processed in the background. In this case, make sure, that the report RBDAPP01 is scheduled in the transaction SM37 as a regular job with the correct variant to process all IDoc´s, which have this processing option maintained.
    --> Trigger immediately
    When using this setting, it is important to have sufficient resources for the immediate processing of the inbound IDoc´s. One dialog work process must be available for every single IDoc.
    If this dialog work process is not available, the IDoc cannot be processed and stays in status 64.
    I reffered the notes
    555229 ‘IDocs hang in status 64 for tRFC with immediate processing’
    734576   ‘IDocs retain status 64, but should be processed immediately’
    1055679 ‘IDoc-tRFC inbound with immediate processing may not work’
    Still the idocs are in 64 status, every time im re-processing them manually. even after re-processing some of them are going to 51 or 54.
    Please help me.
    Regards
    Bhargava Krishna

    Hello,
    Can you please explain your issue is with "Trigger by Background program" or "Trigger immediately"?
    For Trigger immediately, if there is no free dialog work process available than IDocs are posted with status 64.
    For Trigger by Background program, Background job RBDAPP01 will process IDocs depending on variant you define to select & process IDocs(i.e., IDoc Status = 64).
    It is always recommended to use "Trigger by Background program" for high volume interface which has large number of IDocs.
    Help on RBDAPP01
    Regards,
    Sameer

  • Idocs are not processed in the right order.

    Hi,
    I face a problem that when there are a large number of IDocs (Inbound) posted the Idocs are not processed in the right order.
    Msg type: MBGMCR
    any idea how this can happen?
    what is the solution?
    br
    Karen

    No answer

  • Idocs are unable to transfer from R3 to PI system, IDOC status is 03

    Hello Gurus,
    Idocs are unable to transfer from R3 to PI system, IDOC status is 03
    in sm58 getting below error
    RFC  are working fine
    "EDISDEF: Port SAPCEP segment defn Z2SH_DESCR000 in IDoc type MATMAS03 CIM"
    Regrds
    vamsi

    Hi,
    I am also facing same problem, Can any one suggest me what is the issue..

  • Inbound Idocs are not Processing

    Hi,
    Inbound IDOCS queue is not processing if any one IDOC is showing amber(error) . Please let me know the resolution to avoid this issue or let me know the BASIS setting to avoid it.
    Regards,
    PVK.

    Hello,
    Can you please explain your issue is with "Trigger by Background program" or "Trigger immediately"?
    For Trigger immediately, if there is no free dialog work process available than IDocs are posted with status 64.
    For Trigger by Background program, Background job RBDAPP01 will process IDocs depending on variant you define to select & process IDocs(i.e., IDoc Status = 64).
    It is always recommended to use "Trigger by Background program" for high volume interface which has large number of IDocs.
    Help on RBDAPP01
    Regards,
    Sameer

Maybe you are looking for