SO from PO using idocs --same sap client

Hello SAP Gurus,
We need help with the following .
The requirement is we need to create the Sales order from Purchase order using idocs within the same client .
We created the partner profile of the customer and the vendor .
Customer ---maintained an inbound parameters with message type ORDERS and process code ORDE
Vendor -
maintained outbound parameters with message type ORDERS and idoc type ORDERS05 and process code ME10 .
Now when we create the PO and check the status in WE02 we get the error status 56 , EDI: Partner profile inbound not available.
What could be the posible cause of the error .
Anybody with some suggestions and solutions .
Thanks
Honey

Hi,
>>>Now when we create the PO and check the status in WE02 we get the error status 56 , EDI: Partner profile inbound not available.
this means that the partner profile was not created correctly
I'd suggest using logical system as a partner profile
my book contains PO and SO partner profile creation
http://www.sappress.com/product_basic.cfm?account=&product=H3059
Regards,
Michal Krawczyk

Similar Messages

  • Steps to create SO from PO using IDOCs..

    hi frnds..
    i have to create a SO from PO with in same client.
    PO>IDOC>SO..
    IDOC is of type orders05..
    regards..

    Hi,
    >>>Now when we create the PO and check the status in WE02 we get the error status 56 , EDI: Partner profile inbound not available.
    this means that the partner profile was not created correctly
    I'd suggest using logical system as a partner profile
    my book contains PO and SO partner profile creation
    http://www.sappress.com/product_basic.cfm?account=&product=H3059
    Regards,
    Michal Krawczyk

  • Two web apps using the same EJB client jar

    I am currently deploying two web apps on a server. Both web apps use an EJB client
    jar (the same jar) to access EJB's and both apps work when tested independently.
    The problem arises when I log into app A and then log into app B. As soon as
    I do app A loses it's references to the EJBHomes, and other classes.
    It seems a classloader is unloading the first classes and instances loaded by
    the first app and then loading them from app B's client.jar.
    If I put the client.jar in the system classpath everything is fine, but that's
    just a hack.
    Is it not possible to deploy two web apps on a server using the same client.jar's
    in their own WEB-INF/lib's?

    Joe,
    As Pravin mentions, the checking of those boxes in Workbench triggers scheduled jobs within the EAC that kicks off the scripts at the appropriate time/day. But as you've noticed, there's not a ton of flexibility and you don't get cron or Windows Scheduler-type capabilities.
    If you need to do something special, you can manually kick off the report generation scripts from your control directory using the runcommand.bat (or sh) script or place the command into a cron/Windows Scheduler job:
    For example, to kick off the WeeklyReports job, you would do this:
    runcommand.sh WeeklyReports runSo, assuming you go down the route of creating multiple ReportGenerators and scripts, you would create a job to kick off the new script you've created at the appropriate time.
    Hope that helps,
    Patrick
    http://branchbird.com

  • CALL a report from WDA using SUBMIT to sap-spool

    Hi,
    I need to call a report from one of the methods of a WDA application.
    The out of this report is a sapscript. I want show it in WDA (PDF).
    The report is called when a user clicks EXECUTE button.
    The piece of the code is:
      call function 'GET_PRINT_PARAMETERS'
        exporting
          immediately            = 'X'
          new_list_id            = 'X'
          no_dialog              = 'X'
          receiver               = sy-uname
          release                = 'X'
          sap_cover_page         = 'X'
        importing
          out_archive_parameters = t_arcpar
          out_parameters         = t_pripar
          valid                  = i_valid
        exceptions
          archive_info_not_found = 1
          invalid_print_params   = 2
          invalid_archive_params = 3
          others                 = 4.
          submit hbrcced0
                          with pnppernr-low eq i_pernr
                          with pnpbukrs-low eq t_p0001-bukrs
                          with pnpbegda     eq i_begda
                          with pnpendda     eq i_endda
                          with p_expot      eq ''
                          with ano          eq v_gjahr
                          with respcc       eq v_sachn
                         to sap-spool
                         spool   parameters t_pripar
                         archive parameters t_arcpar
                         without spool dynpro
                         and return.
        if sy-calld eq ''.
          message 'err' type 'E'.
        else.
    If i execute this code in WDA, the sy-calld never is equal 'X'.
    But if i execute it in program (SE38) the sy-calld is 'X'.
    How i can call the program 'hbrcced0' in WDA ?
    Cheers,
    Silvio Galery

    Hi Silvio,
    a submit REPORT to spool does work from WDA.
    ONLY when "and return" is used.
    You have that, so it should work.
    Note you had print immediate on, so it will be output on printer,
    and not available to read after the call.
    (which option was the keep after print?, I would have to check docu)
    The sy-calld will be set to X  inside the REPORT when it is running.
    After the submit has run back inside WDA it is of course reset to space again.
    Cheers
    Phil.

  • Using the same client for both regfree and out-of-proc COM

    Hi,
    Here is the context:
    1. We have the same set of COM objects that can be deployed as in-proc COM servers (dlls) or out-of-proc COM servers (exe).  In-proc servers are called through regfree COM.
    2. We have test projects that use the in-proc COM servers through regfree COM.
    I would like to use the same test client projects for both regfree and out-of-proc COM servers (but not at the same time). For example, I would like to first run the client using regfree COM, then delete the in-proc dll and register the out-of-proc com server,
    and then run the client again without having to recompile.  But I have not found a way to do this.
    Instead, what I have to do is modify the project settings of the test client project, removing the regfree stuff (the manifest dependencies) before I can use the test client project with the out-of-proc server.
    Is there a way to do this without recompiling?
    FYI, I have tried regfree COM by changing the client project's Project->Properties->Linker->Manifest file->Additional Manifest Dependencies, or by changing the client project's Project->Properties->Manifest Tool->Input and Output->Additional
    Manifest Files.  Either way works with regfree COM.  And either way I have to remove those settings before making it work with out-of-proc COM (and hence recompiling, which is what I am trying to avoid).
    Thanks,
    Nick

    Try Manifest Tool > Input and Output > Embed Manifest = No, and change Linker > Manifest File > Manifest File to drop ".intermediate" in the middle (or just rename the file after the build).
    A manifest doesn't have to be embedded into the executable, it could be a standalone file named like ApplicationName.exe.manifest and sitting in the same directory next to the .EXE. Then you can simply delete or rename it back and forth to switch between
    registered and reg-free COM.
    Igor Tandetnik

  • CRM-XI integration using Idoc

    Hi all,
    I search document that describes, how to connect XI from CRM using Idoc.
    I`ve found an Description, but using BC.
    which RFC destination type should be use (TCP/IP-Connection Destination type ? or logical Destination type? or ..)
    Which setting I'd like on CRM site ?
    Which Connection parameter I'd Llike ...
    Thanks in Advence.
    Regards.
    Lemin

    Hi
    Go to https://websmp102.sap-ag.de/instguides->mySAP Business Suite Solutions->mySAP CRM
    CRM Learning-
    https://websmp203.sap-ag.de/rkt
    Check here-
    SRM/CRM/XI
    CRM Middleware & XI
    Go to https://websmp102.sap-ag.de/instguides->mySAP Business Suite Solutions->mySAP CRM
    also check
    http://www.sapgenie.com/mysap/crm/index.htm
    http://www.sapgenie.com/mysap/crm/middleware.htm
    http://eai.ittoolbox.com/groups/technical-functional/webmethods-l/sap-exchange-connector-xi-364858#
    http://help.sap.com/saphelp_crm40/helpdata/en/c3/95fc381478ab6fe10000000a11402f/frameset.htm
    For XI
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
    BW WITH CRM:
    http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/af/ed833b2ab3ae0ee10000000a11402f/frameset.htm
    Check threads for possible 'error' handling:
    CRM Data source issue with Delta Load( For BW Gurus only)
    Re: Activities : 0CRM_SALES_ACT_1
    Re: CRM Service Contracts : no records with 0CRM_SRV_CONTRACT_H
    Thanks !!
    Questions are welcome here!!
    Also mark helpful answers by rewarding points
    Regards
    Abhishek Agrahari

  • 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

  • How to create an inbound Idoc from an inbound IDoc in same client

    How to create an inbound Idoc from an inbound IDoc in same client
    Idoc will come from XI as an inbound idoc to SAP, now I have to read this inbound Idoc and split it into Several Inbound Idocs and now needs to be posted in the same client.
    please let me know the procedure..
    Thanks in advance,
    Sagar

    Hi Sagar,
    Develop a cusom Z-Inbound function module, configure the Z-FM to trigger when idoc is recieved from XI. In your Z-Inbound function module split the idoc (Recieved from XI)  into respective Idocs and Using MASTER_IDOC_DISTRIBUTE post the IDOCs into the same system.
    Thanks & Regards

  • Steps of EDI is used to transfer IDOC from R3 system to non sap system

    Hi Experts,
    Can you provide me Steps to configure EDI is used to transfer IDOC from R3 system to non sap system?
    Full points will be assigned.
    Thanks in advance!
    Sapna

    Hello,
             The EDI Configuration required to be done for Transfering IDoc to non SAP System is.
    1. First of all, we need to identify the Transaction Data which is required to be Transfered to external System.(Ex: Sales Order Data or Shipment Data or Delivery Related Data).
    2. Secondly, Identify the IDoc Type & Message Type. IDoc Type can be found in Transaction WE30 & Message Type Can be explored in Transaction WE81.
    3. After that, assign the IDoc Type to Message Type in WE82.
    4. Identify the Selection Program (Outbound) which is generally a Function Module in the Form of IDOC_OUTPUT_<Message Type>. Example, if the Message Type is ORDERS, the FM will be IDOC_OUTPUT_ORDERS.
    5. Assign the Function Module to a Process Code in WE41 (Process Code for Outbound).
    6. Configure Port Definitions in WE21 for which the RFC destinations are to be maintained in Transaction SM59.
    7. Maintain Partner Profiles for the Outbound Message Processing in WE20.
    8. Last, but not the Least, we need to Focus Mainly on Message Control Configuration which is nothing but maintaining the Output Type for the Outbound IDoc to be Triggered for the Sales Order Application or Delivery Application.
       i. In Message Control Configuration, we'll maintain
          a. Condition Tables
          b. Access Sequences
          c. Output Types
       ii. To Create the above elements, we can go to SPRO Transaction and do the same depending on the Application Area such as Sales / Shipping / Logistics Execution etc.
       iii. For Output Types & Access Sequences, we can go to the Transaction NACE or VK01 in which we'll maintain the Output Types / Access Sequences & Condition Records.
       Please note that all the above steps may not be needed if we are using some of the Standard Elements provided by SAP such as Message Type, Process Code, IDoc Type & Selection Program as many of the Standard SAP Applications have their own Elements for different Application Areas.
       For example, if you want to send an Order Confirmation IDoc when the Sales Order is saved, you can use the Message Type ORDRSP, IDoc Type ORDERS05 & Selection Program as IDOC_OUTPUT_ORDRSP.
       However, Message Control Configuration is the Key Factor and is required for all the Applications as per the Customer's / Client's Requirements.
    Hope the above procedure was clear.
    Thanks and Regards,
    Venkat Phani Prasad Konduri

  • How to upload the data from XML file to SAP database using IDOC

    Hi,
    I need some steps  to upload  data from XML format file from other directory to SAP database using IDOC.
    how to approch this please if any one knows give me ans
    it will be a great help ful to me
    Thanks in Advance
    Mallik

    Thank you vijay,
    But i heard that by using this Fun modules, when we are passing IDOC in back ground schedule,  so some other depended FM not supporting, so how to approach this and how to avoid this problem. 
    Have you worked on this before if any one worked on this please help me out
    And thank you once again for your valuable information
    Best Regards
    Mallik

  • Transfer article master from SAP R/3 To External Systems(Futura) Using IDOC

    Dear Experts
    Please let me know  how to  Transfer article master from SAP R/3 To External Systems(Futura) or text file Using IDOCs.
    thanks

    Hello,
    Since you want to transfer Article Master, it should be a Retail System. So you should use Message Type ARTMAS. For fullbuild, you can use transaction WDBM and for changes, you can use WDBU.  For changes, you can enable change pointers for required fields using BD64.
    Thanks,
    Venu

  • IDOC data transfer between 2 SAP Clients on same system

    HI All,
    i was transferring data through standard IDOC from table A609 in client 100(say) to client 301(say).
    Sender    u2013 100  (sender side)
    Receiver u2013 301  (receiver side)
    I did all configurations that were required for transferring data.
    But at receiving side i.e. client 301, data is not populating in the table A609.
    The status at sender side is:
    status 03: Data Passed to port OK.
    But the status is at the receiving side is:
    status 64: IDOC ready to be transferred to application (yellow light)
    My query is why the data is not getting populated in table at receiver end.
    Waiting for your responses.......

    Hi,
    Instead of using idoc ..
    You can write code in RFC function module and update the table directly.
    If it is a Application i mean transaction back end many tables need to update on that case Idoc is necessary other wise use RFC preferabble,
    Program RBDMANI2 for status 51 & 52
    Program RBDAPP01 for status 64 ,66                       "Run this Program By Passing Idoc number it will turn to Green and Table wil be updated
    Program RBDAGAIE for status 32 and 69 (Edited IDocs)
    Program RBDSYNER for status 26
    Program RSEOUT00 for status 30
    re-process IDocs failing in 29 status, use program RBDAGAIN.
    transactions WEINBQUEUE and WEOUTQUEUE to control the individual queues
    Regards,
    Prabhuads

  • [svn:bz-trunk] 21394: bug fix for watson 2887837 Not getting duplicate session detected error when same flex client id is used from two different HTTP sessions in CRX .

    Revision: 21394
    Revision: 21394
    Author:   [email protected]
    Date:     2011-06-16 12:34:13 -0700 (Thu, 16 Jun 2011)
    Log Message:
    bug fix for watson 2887837 Not getting duplicate session detected error when same flex client id is used from two different HTTP sessions in CRX.
    get the sessions id before we invalidate the duplicate session.
    Checkintests pass
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseHTTPEndpoint.java

    For our profect I think this issue was caused as follows:
    Believing that remoting was full asynchronous we fired a 2 or 3 remote calls to the server at the same time ( within the same function ) - usually when the users goes to a new section of the app.
    This seemed to trigger the duplicate http session error since according to http://blogs.adobe.com/lin/2011/05/duplication-session-error.html  two remote calls arriving before a session is created will cause 2 sessions to be created.
    Our current solution ( too early to say it works ) is to daisy chain the multiple calls together .
    Also there seemed to be an issue where mobile apps that never quit ( thanks Apple! )  caused the error when activated after a few hours.
    I guess the session expires on the server and the error above occurs on activation.
    So the mobile apps now ping the server with a remote call when activated after sleeping for more than one hour.
    All duplicate http errors are silently caught and reported.
    Fingers crossed we won't get any more!

  • Configuring AAA network client on ACS v5.1 using the same RADIUS atributes from ACS v3.3

    Hello,
    I was wondering if i should use the same RADIUS VSA attribute on ACS v5.1 to authenticate AAA clients as those i was using on my old     ACS v3.3 server.
    Exemple : under ACS v3.3 i was using RADIUS (Cisco Aironet) attribute to authenticate AP & WLC, should i do the same under ACS v5.1 ?
    Best regards.

    Hello,
    When defining AAA client on the new ACS 5.x server you just select TACACS+ or RADIUS. We no longer define the RADIUS "vendor"/"VSA" when creating the AAA Client entry. All AAA client would be defined as RADIUS or TACACS+ only.
    If you were using specific VSA Attributes then you need to send those attributes back configuring Authorization Profiles on the ACS 5.x. You will find the specific VSA attributes there. Refer to the following screenshots:
    And here are the available attributes for the ACS for RADIUS Aironet:

  • Configuring AAA network client on ACS v5.1 using the same atributes from AC

    Hello,
    Actualy i'm new to use ACS v5.1 and i wanted to do the same AAA client configuration as it was configured on my old ACS V3.3 server.
    My old ACS v3.3 AAA clients type are WLC, LAP and Autonomous AP (using RADIUS (Cisco Aironet)) authentication protocol, PIX & a Router (using TACACS+ (Cisco IOS)) authentication protocol.
    I'm using PEAP_MS-CHAP v2 as a RADIUS authentication method.
    Can any one guide me to accomplish this configuration please ?.
    Best regards.
    Posted by WebUser Mourad Lafjer

    Hello,
    When defining AAA client on the new ACS 5.x server you just select TACACS+ or RADIUS. We no longer define the RADIUS "vendor"/"VSA" when creating the AAA Client entry. All AAA client would be defined as RADIUS or TACACS+ only.
    If you were using specific VSA Attributes then you need to send those attributes back configuring Authorization Profiles on the ACS 5.x. You will find the specific VSA attributes there. Refer to the following screenshots:
    And here are the available attributes for the ACS for RADIUS Aironet:

Maybe you are looking for