Receive IDOC INVOIC even if GR based IV is flagged while creating purchase

Hi,
I created a Purchase order by selecting the flag for GR Based IV. Now I would like to receive Invoice before GR is created through IDOC via EDI. Is there any SAP note to receive and park the IDOC when the GR based IV is selected in PO.
Regards,
Sagar

the programs that post the IDOC just do what they can do based on the information available in the IDOC itself, and it they cannot do it, then an error is issued and the IDOC fails.
turn you process. instead of directly posting the idocs and wanting the failed ones go into the parked status, park all first and process then the parked invoices.
check OSS Note 501524 - EDI: Parking incoming invoices by default

Similar Messages

  • BADI to uncheck Invoice indicator and set net price as 0 while creating PO

    Hi all,
    Is there any BADI to uncheck the Invoice indicator and set the net price as "0" while creating Purchase order?
    Im creating Purchase order in SRM and for certain vendor and material group net price should be set to zero and invoice receipt to be unchecked so that user wont get invoice receipt.
    Can anyone tell me how to do this?
    Thanks,
    Amal

    Pradeep,
    Thanks for your response.
    I will tell you the actual senario im having.
    Using Shoppin Cart, user will order for some items in SRM and once it was completed PO will be created in R/3 system. Here(R/3) when i check in ME23 for the created PO, the IR flag has been set. But i want the PO should be created as IR flag not checked and amount is changed to ZERO for certain vendor and material group combination.
    I searched some threads and found few function modules ( BBP_PD_PO_GETDETAILS, BBP_PD_PO_UPDATE, BBP_PD_PO_SAVE) which can be used in BADI BBP_DOC_CHANGE_BADI. But im not aware of the fields in which we can found vendor, material group, amount, IR indicator.
    Can you please guide me how to resolve this?
    This is my first task in SRM and im not aware of all terms in SRM.
    SRM version: 4.0
    R/3 version: ECC 5.0
    Thanks,
    Amal

  • Changing std title based on Document type while creating po(me21n)

    Hi experts,
    when we enter me21n,there the std title is Cretae purchase order.Here requirement is whenever i select document type as standard po then in std title it should display "Standard po created". Changing the std title in me21n based on selected document type.for eg:if i selected doc type as "stock transport ord" then in std title bar system should display "Stock transport ord po created".
    Thanks in advance.

    Hi,
    You can define allowed item categories for purchase order and doc type config for po
    SPRO>MM>PUR>PO>DOC TYPE>SELECT DOC TYPE>ALLOWED ITEM CAT
    BR
    Diwakar

  • Send/receive IDOCs to SOLMAN system using AS2 protocol!

    Hi All,
    I want to send/receive IDOC file to/from web based SOLMAN system. Currently I'm using FTP server to send/receive IDOC file.
    As of now the current process is to send the IDOCs from ECC to FTP server and from FTP to third party and vice-versa. But due to some constraints, I'm bound to use web based SOLMAN system. Please, can you let me know how to send/receive IDOC files to SOLMAN. Is there standrad FM/method to connect to SOLMAN from ECC as in case of FTP we have FM 'FTP_CONNECT'. Heard that same functionality in case of SOLMAN can be achieved  through AS2 protocol.
    Kindly help.
    Thanks.
    Regards,
    Mukesh

    Hello Patrice
    We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
    Since your que is three years old, I'm sure you must have found some method for this.
    We'll highly appreciate your help.
    Regards: Gaurave

  • EDI - Incoming Invoice Error and GR based Invoice Verification - 51 No GR

    Hi,
    We are implementing EDI for incoming invoices and use Goods Receipts based Invoice Verification.  When processing an inbound IDOC Invoice (type INVOIC01) where the Goods Receipt has not yet been posted, then Inbound IDOC is siiting at Error Status, 51 - No GR documents found.
    Is there any way we can process this as a Parked Invoice or for Verification in the background (MIRA)?  because the current situation is a problem, as 95% of our Inbound Invoices will be received electronically before the Goods are Received. 
    The actual Vendor's delivery note is stored in the segment E1EDP02 (Qualifier 016), field BELNR.
    Currently the IDOC as to sit in error until the Vendor's Delivery Note is Goods Receipted which can be several days later - SAP OSS Note 393883 fro 2001 suggests doing this, but surely this is a common situation.  The IDOC sitting in error in WE02 in the list of IDOCs is difficult to isolate from true errors.
    If this is was mnaul Invoice it could be processed through MIRA for background Invoice Verification later with program RMBABG00.
    We havd SAP version ECC 6.0
    I have spotted OSS Note 501524 which implies that is possible automatically Park Incoming EDI IDOC Invoices, has anyone tried this?  and what would be the transaction/program that could be used to post several at once when the GR has been processed (similar to RMBABG00)

    Hi ,
    You can use the program   RBDMANI2   which will reprocess all the IDOCs (EDIinvoices )that have failed . You can schedule this program in the background and it will post all failed invoices which have the GR posted later .
    We had the same scenario and we have scheduled this program as a daily job at night .
    Regards,
    Hari.

  • Sender and Receiver IDOC config Settings

    Guys I have just come up with this document as a quick reference guide to enable me to be able to configure IDOC scenarios quickly and efficiently. Couls you please let me know if this looks ok and all is in the correct order.
    <u>Quick Guide to Scenarios</u>
    Note A Ports only purpose is to allow either the SAP R/3 Backend system to establish an RFC connection with XI or allow the XI to establish an RFC Connection with the Receiver SAP R/3 system.
    Note An RFC Destinations purpose is to: A) Communicate with the SAP system
    B) Pull metadata from either the Sender/Receiver SAP R/3 System or another reference system that contains the same IDOC.
    <u>Sender IDOC Scenario</u>
    When configuring an IDOC Sender adapter there are a few things that you need to configure before you even start with the Config Directory itself.
    Because IDOC Adapter resides on the ABAP stack no sender agreement or sender Comm Channel is necessary
    Your main configuration is in R/3. You configure R/3 to send the IDOC to XI so hence you don’t need an IDOC Adapter or Comm Channel.
    1.     You need to define an RFC destination to XI in the R/3 Backend system. (SM59).  This RFC destination is used to retrieve the IDOC metadata from the sender system. The IDOC adapter needs these metadata to create the corresponding IDOC-XML message from the RFC stream.
    2.     Assign the destination to a Port in the R/3 Backend system (WE21)
    3.     Define your Partner Profiles for the IDOC you are trying to send and Reference that Port there as well (WE20)
    Based on the above conditions, you do not need a Sender Comm Channel for IDOC or a Sender Agreement for the business scenario. Your only configuration in the Config Directory is to define R/3 as a Business System (no Comm Channel) and define the Receiver Business System along with the Receiver Determination, Interface Determination and Receiver agreement.
    <b><u>I'm not sure if this step is necessary in the sender IDOC scenario</u></b> -
    In XI box you must also define the ports in IDX1 which allows you to establish an RFC connection to pull the metadata in from the backend system, by specifying the RFC destination from where you want to get the info from. This system is defined by the sender port and the client in the IDOC control record. It is either the sender SAP system or an SAP reference system.
    There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
    <u>Receiver IDOC</u>
    When you receive an IDOC things are a little more complex. You do need a Sender agreement and Comm Channel defined. Again there is much to be done in XI and the R/3 Receiver system before you get to the configuration of the Config Directory.
    1.     In XI you must configure the RFC destination which enables XI to communicate with the Target System (SM59)
    2.     In XI you must then create the port which allows you to establish an RFC Connection. In this port you define the RFC destination you previously defined. (IDX1)
    3.     You then must also ensure that a Partner Profile has been established in the Target system which allows XI to send IDOC’s to the Target system. (WE20)
    Once the above is completed you can then continue to configure your IDOC scenario in the Config directory. In your Receiver Adapter you reference both the Port and RFC destination that you just established along with the Release which is to be the Target systems release. You must also specify an Interface version which again is the Target systems version.
    There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
    Apart from the above the rest of the steps in the Config Directory are as normal.<b></b><u></u>
    Message was edited by:
            Alex Ong

    Hi,
    As per my knowledge you need to configure port in IDXI in XI to pull the metadata.
    Its a mandatory step to pull the metadata whatever be scenario like whether you  are sending an IDoc or receiving an IDoc.
    So please configure RFC destination, IDX1 and IDX2 in XI side.
    Only after pulling the IDoc metadata you can proceed with any of the IDoc scenario.
    Whenever there a IDoc is changed you need to delete the previous metadata and pull it again. In such situations you can use the already existing port in IDX1.
    Hope this helps you out.
    Thanks and Regards,
    Vineetha

  • Receiving IDOC from Legacy

    Hi guys,
    I have requirement that POD will be send by the customer to the legacy system, where order processing is happening.
    The legacy system will send the POD to the ECC system by using EDIFACT.
    there is a integration layer where EDIFACT will be converted to IDOC.
    Does the legacy sytem sends the IDOC automatically after conversion to ECC, or do we need to use any function module for this to receive IDOC in ECC.
    If the Legacy system is sending the IDOC automatically in the ECC, where does it post to which table it has to update.
    do we need to do any setting for this.

    Hi,
    There is no BAPI that will split the IDoc and post. You have to do it manually. One way is
    1) Split the IDoc into two or more IDocs based on the maximum items you need. Later post these IDocs.
    2) Post FI invoices as and when you reach max count(without actually creating new IDocs).
    I guess first one would be better as you can tract which IDoc resulted in which FI document(Invoice).
    I worked on this before. When we process an IDoc with more items, we flag that IDoc with a custom message with status 51. We have a scheduled job that picks the IDocs with this status and split the IDocs to 2 or more new IDocs.
    These new IDocs are processed later.
    Hope this helps
    Vamsi

  • How to process the Received Idoc in SAP R/3 ? What to be done ?

    Hi All
    I am working for file to Idoc scenario.....
    Idoc received into SAP R/3 but how to process the Idoc data ?
    Such it will store in SAP R/3 DB.....
    Clearly
    How to Process the received idoc data into SAP R/3 ? (this is for inbound idoc)
    I hope any one can help me on the processing steps ?
    Waiting for valuable inputs form experts
    Regards
    Rakesh

    rakesh
    chec <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">Sample IDoc</a>
    normally, based on the idoc types it will get processed. if it is an idoc with master record it will create appropriate master records or if it based for a transaction it will create one.
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098</a>

  • IDocs, INVOIC partner profile configuration

    Hi,
    I need to receive the INVOIC IDocs from sender system.
    Sender(S) system is new system
    receiver(R) system is already exisitng system.
    I tried to configure the inbound settings in receiver syste. But message type INVOIC, process code INVL, FM all are already available and configured for some ohter systems.
    Now if i configure only partner profiles and distribution model, then is it work.
    Thanks
    Kiran

    Kiran,
       INOVOIC, INVL, Process codes etc come with the standard system. They can be configured for any partner profile and any sender system.
    First, you need to determine the inbound connection. Will the new sender system (S) going to follow the same RFC connection already setup for other sender systems? E.g. Are all the inbound IDOC's flowing through PI or a single EAI system?
    If yes, then you just need to setup a new partner profile and use the same port already setup for your existing connections.
    If no, then you have to determine how the sender system will connect with SAP. Will they drop files in the SAP's application server? After dropping can they execute the startrfc.exe with required parameters. If they can then you can just proceed with creation of a port to listen that folder (assuming the RFC connection is already setup for that connection) and move ahead with partner profile creation and other mandatory setups. If they cannot trigger the startrfc.exe, then you have to define a new RFC destination (SM59) and a new port (WE21) to read data for this RFC destination. You have to determine when to read the data (e.g. explicit host type etc).

  • IDOC: INVOIC - for more than one purchase order

    Hello Experts,
    I have an IDOC INVOIC for incomming invoices.
    The problem is, that in case of more purchase orders (GR was posted with the same delivery number!) the IDOC can not be posted, because it just finds the first PO (invoiced quantity higher than GR quantiy).
    How can i reach, that the IDOC finds all PO with the same delivery number (from GR) und splits up the the relevant purchase orders!
    In Segment E1EDP02
    i have qualifier 016
    and BELNR = is the delivery numner by GR (the delivery numner is the same for all POs).
    Many thanks in davance,
    Hannes

    Hi Prashant
    1-I accessed form Setup > Transactions > AutoInvoice > Grouping Rule and removed (Group by) Data at the table
    2-at system opiton i made this rule used
    3-i Created 2 sales orders and shipped it
    4-Post to the Receivables
    it generates 2 invoices for every sales order not one invoice for the two sales order
    what's my error
    Regards
    Amr Hussien

  • Receiver IDoc Adapter - Outbound IDocs in IDX5 but stucked in SM58

    Hi Gurus,
    I have a Receiver IDoc issue with the above error.
    My message is successful in the IE pipeline (but with error on outbound side)
    I can even view the generated IDoc numbers for those messages in IDX5,   but when double-clicking on those IDX5 entries SM58 is called and there I see the error as follows:
    Caller:  PIAFUSER
    FM:  IDOC_INBOUND_ASYNCHRONOUS
    Status Text: No Authorization to send IDocs with Message Type 0
    The weird thing is why is the caller showing as PIAFUSER, when my RFC destination is using a custom RFC user id.
    Shouldn't it be that the Caller be my custom RFC user id since this is the user used by the RFC destination i specified in the receiver idoc comm channel?
    Would anyone of you know how to resolve this?
    I have already implemented Note 837595 for (a) my custom RFC user id in the target system (b) PIAFUSER and PIISUSER in my Integration Server;  and assigned SAP_XI_APPL_SERV_USER role to PIISUSER also as specified in  http://help.sap.com/saphelp_nwpi711/helpdata/en/d4/d12940cbf2195de10000000a1550b0/content.htm
    I am aware that IDoc should be sent to the receiving system by using the IDoc adapter and NOT by using the IDoc Interface (tRFC port)
    Thanks in advance

    Hi All,
    I resolved this on my own.
    The steps i specified in my 1st post (Note implementation & Role assignment) was not enough, we had to assign SAP_ALL & SAP_NEW to the rfc user.    The Note implementation & role assignment should have solved this problem, but strangely it was not enough.
    As for the question on why PIAFUSER is showing up as the caller and not the RFC user id used in the rfc destination used by the port, it's because the original caller is what gets recorded in SM58, in this case Receiver IDoc adapter on the AE so PIAFUSER,   and not the RFC user id.   you can verify this in table ARFCSSTATE
    Thanks to all answers

  • Receiver Idoc adapter - issue

    Hi,
    I need to send an IDoc (CRMXIF_ORDER_SAVE_M01) to SAP CRM. The trouble occur when having/wanting to use/send only the segments that apply to release 620.
    In order to do that I have in my receiver IDoc adapter specified the value '620' in the Segment Version part.
    As soon as having done this my IDocs fail in the adapter giving me the following error:
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>Segment 'E101CRMXIF_ACTIVITY_X', segmentnumber '000001' not correct in structure CRMXIF_ORDER_SAVE_M01</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: Segment 'E101CRMXIF_ACTIVITY_X', segmentnumber '000001' not correct in structure CRMXIF_ORDER_SAVE_M01</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The segment specified in the above corresponds to the very fist sub-segment to the main segment (BUSTRANS). So if removing that segment the error jumps to the next segment (which would then be the first sub-segment).
    Should be noted that I have no trouble sending IDocs if I've either not specified a Segment version (meaning latest version is automatically used) or if I explicitly request the latest by entering the latest segment release (700 in my case).
    <Trace level="1" type="T">Convert one IDoc</Trace>
      <Trace level="2" type="T">Convert Control Record</Trace>
      <Trace level="2" type="T">Convert Data Records</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_BUSTRANS</Trace>
      <Trace level="2" type="T">Ignore unknown Segment E101CRMXIF_BUSTRANS</Trace>
      <Trace level="2" type="T">Ignore segment field: APPL_SNAME</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_TASK</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_GUID</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_ID</Trace>
      <Trace level="2" type="T">Ignore segment field: PROCESS_TYPE</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_TYPE</Trace>
      <Trace level="2" type="T">Ignore segment field: POSTING_DATE</Trace>
      <Trace level="2" type="T">Ignore segment field: DESCR_LANGUAGE</Trace>
      <Trace level="2" type="T">Ignore segment field: DESCR_LANGUAGE_ISO</Trace>
      <Trace level="2" type="T">Ignore segment field: LOGICAL_SYSTEM</Trace>
      <Trace level="2" type="T">Ignore segment field: CRM_RELEASE</Trace>
      <Trace level="2" type="T">Ignore segment field: CLIENT</Trace>
      <Trace level="2" type="T">Ignore segment field: CREATED_AT</Trace>
      <Trace level="2" type="T">Ignore segment field: CREATED_BY</Trace>
      <Trace level="2" type="T">Ignore segment field: CHANGED_AT</Trace>
      <Trace level="2" type="T">Ignore segment field: CHANGED_BY</Trace>
      <Trace level="2" type="T">Ignore segment field: LOCAL_TIMEZONE</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_ID_OK</Trace>
      <Trace level="2" type="T">Ignore segment field: HIGHEST_ITEM_NO</Trace>
      <Trace level="2" type="T">Ignore segment field: CRM_CHANGED_AT</Trace>
      <Trace level="2" type="T">Ignore segment field: CALC_SCHEMA</Trace>
      <Trace level="2" type="T">Ignore segment field: SCENARIO</Trace>
      <Trace level="2" type="T">Ignore segment field: VALID_FROM_EXT</Trace>
      <Trace level="2" type="T">Ignore segment field: VERIFY_DATE</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ACTIVITY_X</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ACTIVITY</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ADDRESS</Trace>
      <Trace level="3" type="T">Segment= E103CRMXIF_ADDRESS</Trace>
      <Trace level="3" type="T">Segment= E107CRMXIF_ADDRESS</Trace>
      <Trace level="2" type="T">Ignore unknown Segment E107CRMXIF_ADDRESS</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ADDRESS_F</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ACT_REASON</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ACT_REASON_F</Trace>
    Hope someone can help me so that I can succesfully limit the segment version used when sending Idocs.
    Best regards,
    Daniel

    Hi,
    Thanks for your quick reply.
    The funny thing is that even if a try to post the exact same idoc (except for the EDI part) that I have received from CRM it still fails in XI with the before mentioned error.
    But to answer your questions:
    1. I'm not using java mapping but traditional message mapping (meta-data are up-to-date and structure is newly loaded).
    2. No blank segments are being created
    3. All segments have value 1 or blank (using blank works fine for me, that is when not trying to limit Segment version. But using 1 makes no difference)
    Best Regards,
    Daniel

  • Inbound SD IDOC invoice

    Dear All,
    I am struggling to find inbound SD invoice IDOC. Any idea which standard IDOC fuc is used ?
    Process - SAP is acting as backend system to receive customer invoice
    I could see IDOCs for FI posting Accounting document
                     Idoc for credit memo
                     Idoc for MM invoice
    But I dont find any SAP standard IDOC, I could find IDOC_INPUT_S1INVOICE_SD byt internally its using IDOC_INPUT_INVOIC_MRM (MM invoice)
    Can anyone help me out in getting correct IDOC for sales Invoice.
    Just to add in VF01 transaction i am looking for to post SD invoice.
    Thanks and regads
    -Indrajit
    Message was edited by:
            Indrajit Chauhan -TCS

    Hi,
    thse are the avaialbe function modules for invoice.
    IDOC_INPUT_INVOIC_FI
    IDOC_INPUT_INVOIC_MM
    IDOC_INPUT_INVOIC_MRM
    Regards,
    Nagaraj

  • Receiving Proforma Invoice Via EDI

    Hi All,
    I have a serious problem. Well I sent to the vendor a requeste for quotation RFQ and he sent to me a Proforma Invoice as a response to my RFQ.
    He created a new message type ZPROFORMA (copy of standard INVOIC) with the IDoc type INVOIC01.
    My problem is that I don't know how to create quotation from this IDoc???
    what Function Module is to use to integrate this IDoc.
    What settings should I check to work with this IDoc???

    First I thank u a lot for ur answer,
    I couldn't find any Function Module to create the quotation from the inbound IDoc.
    Note that the IDoc that i received from the vendor has a message type that doesn't exist in my system ZPROFORMA but has the IDoc type INVOIC01. Now I don't know if I have to develop a new Function Module or should I modify an existing one, or if it is just a matter of settings???
    All I want to know is how can I generate a vendor quotation from this IDoc.
    I found this FM "IDOC_INPUT_QUOTATION_CREATEFRO", is it a FM to create Vendor quotation???
    In the WE42 (transaction to create process code) I found value 'TS00007794' (for create quotation) in IDENTIFICATION field, what does this value mean, can it be useful???
    Thank u in advance.

  • Deleted all IDoc channels but can still receive IDocs in XI

    In our test system I deliberately deleted all IDoc Sender communication channels to test something. I then discovered that the XI system is STILL receiving IDocs!
    I also refreshed the runtime cache. How can this be?
    BR,
    Tony.

    Hi Prateek,
    You said:
    "It is nowhere written that "you do need it"
    The SAP documentation quoted in the previous post clearly states:
    "You require the IDoc adapter to connect SAP systems (or external systems) to the Integration Server using IDoc communication. "
    So it is written that you "do need it", even if it seems you don't.
    And I ask again: Why be given the possibility to create an IDoc sender adapter in the system if you don't need it? There is a basic philosophical question that is not being answered here!
    BR, and thanks so far all for replies,
    Tony.

Maybe you are looking for