Purchase requisition idoc

hello gurus,
i know there are idoc types for purchase requisition create / change. But I am not able to understand how do i trigger that idoc from sap. I dont see any output / message types in purchase requisition ME51. Is it not from message control ? Is it stand alone or ale... i am confused. please help me. i would appreciate if you tell me a quick process to do this

Hi,
I belief that REQOTE is an RFQ (Quotation) not Purchase Requisition. There is no output determination for PR in Sap
I guess you will have to :
- create a transaction/report that read the EBAN table or use BAPI_REQUISITION_GETDETAIL and creates a Z-IDOC.
- create Z-idoc (message and idoc types)
You need to program the filling of the IDOC and maintain the distribution model and partnerfunctions. Use MASTER_IDOC_DISTRIBUTE function model to send your idoc .
Hope it helps,
JG

Similar Messages

  • Idoc to File scenerion : How to trigger Purchase requisition idoc

    Hello ,
    I am working on outbound interface for purchase requisition , which uses Idoc as sender adapeter and the Idoc type being used is PRWQCR03.
    can any one tell be how trigger the idoc purchase requisition idoc .
    Cheers
    Chan

    Hi,
    Go to WE19(testing tool) in the Application System(R/3).
    Then give the necessary parameters like Sender Port/Reciever Port , Message Type and then fill the data.
    Refer this thread-
    IDOC to Suppliers
    Regards,
    Moorthy
    Message was edited by: Krishna Moorthy P

  • How do I enter Document Type for Purchase requisition IDOC

    Hello,
    File - IDOC (PREQCR.PREQCR02)
    The file is getting picked up and shows up a checkered flag in Moni..
    but in WE05, on R3 side, i see an error message
    "Enter Document Type"
    How do I enter document type for Purchase requisition IDOC?
    will that solve this issue?
    thanks and regards
    Nikhil.

    Hi,
    For error 51, you need to set the default document type in the inbound processing FM of the IDOC
    Standard type - NB
    Subcontrator type
    Blank PO
    Service PO
    Stock transport PO.
    Document types is used for below things,
    1. It controls the no. range of the document i.e. the doc no.
    2. It controls whether doc no. is auto assigned or manually entered
    3. It controls the field status of the doc header fields i.e. whether input is mandatory or optional
    4. It controls the physical doc filing
    Thanks
    Swarup

  • Generating and transferring purchase requisition IDoc

    In ECC 6.0 there exists ALE_PR_CREATE which gave us all the required fields for generating the IDoc that we needed to transfer to our JCo program. Once the IDoc was generated using this program, it's status was set to '30' automatically.
    The next step in order to send this generated IDoc to the designated port was to make use of the standard program RSEOUT00 passing the message type so that it sends all IDocs, of that particular message type (PREQCR and PREQDL in our case) and having a status of 30, to the port, changing the status to 12 once this operation is completed.
    Since it was a standard program , I used the same logic in 4.6C. Unfortunately, the function module ALE_PR_CREATE does not exist in 4.6C.
    The alternative was to use ALE_REQUISITION_CREATE and ALE_REQUISITION_DELETE.
    Why 2 Function modules? Here's why...
    The first function module gave us all the required fields except one - the deletion indicator.
    Keep in mind that this field was also provided by ALE_PR_CREATE in ECC 6.0 system thus eliminating the need to look elsewhere.
    So, to satisfy our requirement of getting the deletion indicator for deleted items of a particular Purchase requisition, we found the second mentioned function module - ALE_REQUISITION_DELETE.
    This threw another problem in front of us...
    This function module gave us only the purchase requisition number, item number and deletion indicator. All the other data fields that we required for our java app to process the IDoc were missing.
    In order to solve this issue, we have designed our program to generate 2 IDocs one after the other. First using ALE_REQUISTION_CREATE and next using ALE_REQUISITION_DELETE in sequence.
    This gives us all the fields.
    The next problem was that the generated IDocs were having the status 03 (Data passed to port. OK.) but the Java application never seemed to receive the generated IDocs.
    A search on SDN led me to check the IDoc queue in SMQ1, a case of stuck IDocs in SM58 and also changing IDoc status in BD75 all in vain.
    Finally, on debugging the RSEOUT00 program, found out that it is checking for the status '30' (IDoc ready to be sent to port) which is hard coded in the program.
    On doing further research on SDN, find some resources that suggested various function modules.
    Tried out all of them one after the other.
    By trial and error, finally stumbled upon the Function Module 'DEQUEUE_ES_EDIDOCS' that acted as a replacement to using the RSEOUT00 program.
    After the IDoc is generated, just passing the IDoc number to this Function module sends it to the port and this was successfully received by our Java app.
    Posting this on SDN for the general benefit.
    Has anyone faced any similar issues? Let us know.

    Hi,
    Im using the non-enjoy  BAPI and BAdI for PR and for deletion the outbound IDoc gets send out all the way but for create outbound IDoc it gets stuck in status 30. I did try the FM that you suggested but doesnt have any effect.
    FMs that is being used inside my BAdI:
    ALE_REQUISITION_CREATE
    ALE_REQUISITION_DELETE
    Thanks,
    Arash

  • Purchase requisitions idoc issue

    Hi,
    We have found a new interesting thing happening in ECC.
    IDOCs does not get processed due to PurReq is being processed.
    Then the IDOC goes into status 51 and can no longer be processed by the batch jobs that is running for status 64.        
    1) Is it possible to keep the status as 64 for these types of errors?
    2) If not is it possible to reset these IDOCs from 51 to 64 in a batch job
    3) or is it possible to get the batch job to run for IDOCs with status 51?
    Regards,
    RSK

    Hi,
    new !
    that's just the normal behaviour since... almost the beginning of IDoc history.
    1. yes. program RC1_IDOC_SET_STATUS.
    2. yes, but that's not recommanded, as your idoc has been already processed, and it said to you "I cannot update this object  because someone or something is currently treating this same object".
    if it's a permanent error like (this customer does not exist), that means with a background process (with a too short frequency) you will overload your system for nothing with a treatment like:
    "idoc 64 -> 51" + "background change: 51-> 64" + "reprocess: 64 -> 51", etc...
    when it's one idoc, it's ok, but if a day you a complete source files with several idocs which are in error.... you will reprocess them several time to say to you the same thing "cannot update because customer does not exist" (for instance).
    3. yes. RBDMANIN in background, or tx BD87 in foreground.
    According to me, it's better to use BD87 as it's a human you can analyze and decide to retreat the data.
    Use background program only if you are sure that the data (in error) was sent a 2nd time after. In your case of purch req. i did not recommanded that.
    Have a look a that:
    Idoc1: role = change value with A on pruch req 123. This idoc is in error (like in your exm: already processing by another...)
    Idoc2: role  =change value with B on purch req 123. This idoc arrives 5 min after idoc1. but this times the other processing is finished, and so ecc can integrate this idoc2. So in your systm you have value "B".
    And you with your background process which runs (every hour, for instance), one hour after your Idoc2, you will retreat idoc1, and so now for your purch req, the value is "A"... and no more "B" which was the last value sent by your source system. => Problem !
    4. So why not use it, but be clever/smart before to use such a background retreatment. Estimate the pro/cons.
    regards.
    Mickael
    P.S : it's because we can, that we have to do it.

  • Problems for creating a header text in a Purchase Requisition by IDOC

    Hello,
    I´m creating Purchase Requisition by IDOC. I use PREQCR02  like basic type (   Message type PREQCR-Create purchase requisition )
    I don´t have any proble for creating item text, but I can´t create a header one.
    Any Idea?
    thanks for all.

    What is "it" that you cannot do (+ hate)???
    What is "status"? LineStatus???
    What is your problem when you try to skip an item?
    PS: You should always use enums instead of hard-coded values e.g.: Use the BoAPARDocumentTypes Enumeration for delivery.Lines.BaseType

  • Interface-Establishing relation of idoc created and Purchase requisition

    Hi All,
    I have created a program wherein idocs are generated. Its gives rise to Purchase requisition.
    Can you please tell me how to show the PR created against the idocs that are generated in the spool list?
    Please note the function module creating the idocs does not return the PR no. generated.
    Any alternate solution to this is welcome.
    Thanks,
    Abhhishek

    Done

  • IDOC for Purchase Requisition

    Hi Experts,
    I have to triger an IDOC  to a 3rd party system when a Purchase Requisition is created, with the PR data.
    Is there any IDOC to do this?
    I Hope help me,
    Regards.
    MC.

    HI,
    Check these
    The message type is PREQCR.
    The IDOC types are
    PREQCR01 40A
    PREQCR02 46C
    PREQCR03 620
    The function to be used is BAPI_IDOC_INPUT1
    Thanks
    Mahesh

  • How to link Idoc generated with the Purchase requisition?

    Hi All,
    I have created a program wherein idocs are generated. Its gives rise to Purchase requisition.
    Can you please tell me how to show the PR created against the idocs that are generated in the spool list?
    Please note the function module creating the idocs does not return the PR no. generated.
    Any alternate solution to this is welcome.
    Thanks,
    Abhhishek

    Triple-post = Triple-lock.
    Please read the forum rules before posting any further.

  • IDOC to notify changes in Purchase Requisition

    Hi,
    I have a requirement where I would like to generate an IDOC whenever there is a change in Purchase Requisition therough SAP Screen. Is there any idoc available for the same?
    Regards,
    Venkatesh

    Hello Venkatesh,
    I do not think what you are looking for is available readily. SAP provides the following:
    PREQCR01
    PREQCR02
    PREQCR03
    PREQDL01
    What you could do is create a ZPREQCHG IDOC by copying PREQDL01, so you are covered for closing and deletion as well.
    In the header segment  E1PREQDL, create a z segment and include all the fields that you want here.

  • How can create IDOC for Purchase Requisition

    Hi all,
    whenever I change the Purchase requisition(Tcode-ME22N),IDOC has to be generated automatically.Please help me out.

    Hi ravi,
    It seems you are talking about the purchase order change.
    because ME22N is a transaction for editing the purchase order.Purchase req. is a internal document which we dont send out to any one.
    Anyway what is the output type you are using?.
    If you use NEU then no need for any changes.
    otherwise use NACE transaction and select your output type then mark the 'multiple issuing ' flag.
    So whenever there is a change system senses that and proposes the output.
    After that you got to make the settings at the partner profile using WE20 transaction.There at the message control parameters level mention the output type and set the change flag.
    Entry could be EF ( App.id) NEU (output type) and X (Change flag).
    So system generates the IDOC whenever you do the change using ME22n transaction.
    Please let me know if you have any issues.
    Thank you.
    Regards,
    karun.M

  • Error code 083 on LSMW - Purchase Requisition creation

    Hii all,
    I have generated a bapi program for purchase Requisition creation.
    the followings are the programe details:
    Business Object
    BUS2105
    Method
    CREATEFROMDATA1
    Message Type
    PREQCR1
    Basic Type
    PREQCR101
    I have divided the structures into 3 sections:HEADER,ITEM DETAIL,ACCOUNT ASSIGNMENT.In the account assignment group at the "Maintain Field Mapping and Conversion Rules" (E1BPMEREQACCOUNT), wbs element field marked as "move".
    At the "E1BPMEREQACCOUNTX" the wbs field was mared as "X".
    the programm can read the feild & displays the WBS element that it can read from the datafile.
    the problem is that during the stage of " Create IDoc Overview"
    it provides the following error:
    Enter WBS Element
    Message no. ME083.
    I have checked the WBS element& nothing is wrong with it.
    any one can help me out on this?
    thanks
    M S

    Hi Jurgen,
    Thanks for replying.
    1. For BAPI, at step 14. when i execute, it is a warning message
    No Data could be selected
    2. yes, I have activated the IDOC Settings.
    Please suggest.
    Thanks,
    Sahil

  • Automatic Scheduling Agreement from Purchase Requisition

    Hi All,
    Can we craete a Scheduling agreement automatically from a Purchase requisition? The scenario is like we will be craeting a third party Sales order and through ALE/IDOC system will generate a PR. Now we want to create a Scheduling agreement against the same PR automatically. Is it possible to do this through some customization in SPRO?
    Satisfactory answers will be rewarded.
    Thanks
    Indrashish

    Hi Indranish
    Scheduling agreement is long term contract.There is no need to create SA against each  PR (requirement).Normally SA will be created as a long term agreement with supplier and whenever u need the material u can raise delivery schedules against the SA.These delivery schedules can generated by MRP run automatically.
    I don't understand the your business requirement of each PR to be converted to SA.Can u give so more details of your requirement.If the requirements are continuous, user can raise the requisition with document type RV and same thing can be converted in to Outline agreement.
    Regards
    Ramakrishna

  • Problems with a purchase requisition interface via SAP XI

    Hello.
    We are integrating the purchase requisition from external aplication to SAP through SAP XI. SAP XI send a IDOC to SAP R3 to create the purchase document. The conection is made with rfc conection which has set the comunication user and logon language. The purchase requisition is created with the logon language and if the material has not short text in this language in material master the error ME095 is generated.
    I don't understand this error because in the interface we set the PR short text which is posible to change. Also, we have set this system message like warning in T160M.
    We don't find any way to skip this message and we think if the interface allow to set a short text in the PR it's the same that the material master isn't updated with the short text in logon language.
    Thank you very much.
    Alberto

    Hi.
    I don't want to change the short text in Material Master. I only want to change this short description in PR, but if I don't mantain the short description in material master the error ME095 is generated. I need to be able to create a PR independent of logon language.
    Thank you for your answer.
    Alberto

  • Problem with purchase requisition interface via SAP XI

    Hello.
    We are integrating the purchase requisition from external aplication to SAP through SAP XI. SAP XI send a IDOC to SAP R3 to create the purchase document. The conection is made with rfc conection which has set the comunication user and logon language. The purchase requisition is created with the logon language and if the material has not short text in this language in material master the error ME095 is generated.
    I don't understand this error because in the interface we set the PR short text which is posible to change. Also, we have set this system message like warning in T160M.
    We don't find any way to skip this message and we think if the interface allow to set a short text in the PR it's the same that the material master isn't updated with the short text in logon language.
    Thank you very much.
    Alberto

    Hi.
    I don't want to change the short text in Material Master. I only want to change this short description in PR, but if I don't mantain the short description in material master the error ME095 is generated. I need to be able to create a PR independent of logon language.
    Thank you for your answer.
    Alberto

Maybe you are looking for