BAPI_IDOC_INPUT1

Hello,
Does anyone know what is the use of field INPUT_METHOD for BAPI BAPI_IDOC_INPUT1?
Has it something to do with create or change?
I have configure PO inbound scenario but now I need to handle PO change also, so was wondering if I can use this field.
Regards,
Sunil Joyous

No idea about the parameter INPUT_METHOD, but I am sure, if you want change the PO in inbound you have to use the message type PORDCH..I dont think you can crate or change in single message type via PORDCR1.

Similar Messages

  • How to call Z-Function module from BAPI_IDOC_INPUT1.

    Hi All,
    Process code is :BAPI and standard function module is  BAPI_IDOC_INPUT1.
    I am coding all the logic for the INBOUND IDOC in the Z-Function module ZIDOC_INPUT_ZGOODSMOVEMENTOIL.
    My requirement is:
    Process code fires the inbound function module BAPI_IDOC_INPUT1, this in turn call the function module ZIDOC_INPUT_ZGOODSMOVEMENTOIL.
    How can i call ZIDOC_INPUT_ZGOODSMOVEMENTOIL from BAPI_IDOC_INPUT1 to process the idoc.
    Thanks in Advance.
    Regards,
    Umesh

    Hi Krush,
    Thanks for your reply,
    Now i can trigger the idoc.
    I have one more problem that if i want to add another z-segment to the attached idoc type its not allowing me its saying that it is already generated and cannot be changed.
    if i am generating the BDBG transaction its not asking for specific segment and it automatically takes the segment and generates the function module.
    How  i can add an additinal z-segment to the idoc type and it generate through BDBG transaction to include in inbound function module?
    Thanks in Advance.
    Regards,
    Umesh

  • User exit for IDoc MBGMCR - BAPI_IDOC_INPUT1 - BAPI_GOODSMVT_CREATE

    Hi Gurus,
    I just want to ask if there is any user exit that I can use for this IDoc. My requirement is to check if thevalue from E1BP2017_GM_HEAD_01-REF_DOC_NO already exist in MKPF using XBLNR. If this reference document already exist, I need to raise and update the IDoc status into an error.
    Thanks and best regards,
    Andre

    Hi,
    Check the badi "LE_SHP_GOODSMOVEMENT", method "CHANGE_INPUT_HEADER_AND_ITEMS".   Pass the errors in the structure CT_LOG.
    Regards
    Vinod

  • How to create IDOC from Function module or RFC

    Hi all,
            I have tested one inbound IDOC for Time Upload to CAT2 using basic type "CATS_INSERT01"  in WE19 through function module BAPI_IDOC_INPUT1 .It works well.
    Now i need to create this IDOC once the sale order gets created thru BAPI.
    For creation of Sale order i wrote one RFC in which i will call the Standard Sale Order Bapi.My question is once the Sale order gets created in that RFC How do i trigger the IDOC for CATS upload.

    Hi,
    Which SAP product of wich release of which SP are you using ?
    The procedure is documented in help.sap.com and in blogs and SDN forum messages.
    It means that the use of the SEARCH button should give plenty of answers...
    >When I check "Local object" checkbox I get a message "Test objects cannot be created in foreign >namespaces"
    As usual, begin your choosen name with an "Z".
    Regards,
    Olivier

  • Issue in Extension of ARTMAS05 IDoc

    Hi Experts,
    We need to extend the standard IDoc ARTMAS05 to add 70 user specific fields.
    when i'm doing the extension in WE30, i'm getting the below error.
    " Action is not possible for generated IDoctypes"
    in SAP Note 913901 , it says that we can't extend the genarated IDoc types.
    " The extension concept for interfaces in Transactions BDBG and BDFG does not
    work with extensions for the IDoc types created using Transaction WE30.
    When you create extensions in Transaction WE30, the system does not check
    whether the IDoc type for which you are creating the extension has been
    generated.
    You cannot create an extension for a generated IDoc type."
    Please suggest what is the alternative way to extend.
    thanks in advance
    Rahul
    Edited by: Rahul Gautam on Feb 18, 2010 12:01 PM
    Edited by: Rahul Gautam on Feb 19, 2010 3:59 AM

    Hi Anup,
    Thanks for replying. But as per my requirement i have to extend the standard Idoc type ARTMAS05. And as per my understanding BAPI_IDOC_INPUT1 will works and it will trigger another inbound FM inside it. And my requirement will not allowing me to copy the standard IDoc to ZIDoc
    Please reply is there any other option to Extension ARTMAS05.
    Thanks
    Rahul

  • Initial load of articles through ARTMAS05

    Hi Retail experts, I need to built IDOCs to perform the initial load of articles through ARTMAS05.
    Although we tried to use an IDOC from a DEMO system as template, we couldn't get a successful IDOC so far. The Function module we are using is BAPI_IDOC_INPUT1, with IDOC type ARTMAS05.
    Does anybody has a guideline to set this up?
    Thanks in advance.

    I would welcome Bjorn's input on this, but, generally I accomplish this using LSMWs. I use SWO1 to explore the business object, but use LSMW (Legacy System Migration Workbench) to mass load. In the case of LSMW, you simply call the transaction LSMW.
    - From here, define a project, subproject and object. (Eg: Project = INITLOAD {initial data load}, Subproject = LOMD {logistics master data}, object = ARTMAS {article master}).
    - Maintain the object attributes. Here, you can chose from four options: standard/batchinput, batch input recording, Business Object Method (BAPI) or IDoc. Choose the Business Object method, use object BUS1001001 and method CLONE.
    - Define your source structure. Here, you will lay out what the input file's STRUCTURE is going to look like (not the fields). Since it's ARTMAS, it's not realistic to put all data into a single row in a text file, so you will likely use a structured input file - especially for variants, site-specific and sales-org-specific data.
    - Define your source fields. Here you will define the fields that are in your input file and assign them to your input structure. A lot of work goes into this step. Note - I would try to use names very close to the SAP names, since there is an automapping tool. Also, you can copy SAP table structures into your field structures which is very helpful if you plan to use say 75 - 80 percent of the fields of a particluar structure.
    - Maintain structure relations. You will assign your input structures to the corresponding ARTMAS structures in this step.
    - Map the fields and maintain conversion rules. Here you assign your input fields to the ARTMAS fields. Also, you can code ABAP in this step for conversion/translation purposes. It depends on your chosen ETL or ETCL or ECTL or CETL methodology (E = Extract, C = Cleanse, T = Transform, L = Load) on whether you will write ABAP conversion rules in this step.
    - Specify input files. This is where the data resides in it's text file input format. Typically, you will use a small data set that sits on your PC to test it, and then for a mass load, create a server-side directory on the SAP server, place the input file there, and you can use it. This speeds processing for large files considerably.
    - Assign files. Here you assign the previously specified input file to an input structure
    - Read data. This actually reads the data so that you can see how it's going to come in.
    - Convert data. This creates a psuedo IDoc. It is not an IDoc yet, but in IDoc format.
    - Start IDoc generation. This converts the converted file into a true IDoc.
    - Start IDoc processing. Here, your IDoc moves from 64 status to (hopefully) 53 status.
    Well, I hope this helps, and I would be interested in Bjorn's input. Also, Bjorn, what did you mean by the WRKKEY comment? I've never heard or seen a reference to this.

  • Custom - Material Master Update using an IDOC (Message Type - MATMAS_BAPI)

    Hello everyone,
    I was writing a functional specs. Basically, I want to update the material master MM02 using an IDOC (MATMAS_BAPI01 - Basic Type & MATMAS_BAPI - Message Type). This is currently working.
    To my understanding, this currently uses function module - BAPI_IDOC_INPUT1 to update the material master after the IDOC is posted to SAP ECC from XI system.
    Now I want to add one small validation logic before it actually updates the material master (MM02).
    I looked around and found one exit - EXIT_SAPLMV02_002 in enhancement MGV00001. I was almost sure that this EXIT can be used to write the custom validation code before, actual MM02 updation.
    However while trying to establish a link between this EXIT and BAPI_IDOC_INPUT1, I found that EXIT_SAPLMV02_002 is actually a part of another function module - IDOC_INPUT_MATMAS01 and not BAPI_IDOC_INPUT1. I am stuck here if adding the custom logic in the exit really going to work.
    a bit of googling and I found from WE30 that the purpose of both these function modules are actually different. While BAPI_IDOC_INPUT1  actually create & updates the material master (also plant specific master data which is my need), IDOC_INPUT_MATMAS01 is just for maintenence of few fields in MM02 (may be custom fields).
    Can anyone point out if my thing is in right direction?
    Also please offer any solution where shall I put the Custom Logic in the EXIT or the some variants of
    BAPI_IDOC_INPUT1.
    A less technical explanation would be appreciated as I come from a functional background and invloved in this for writing the func specs. I want to make it sure that what I write is not useless and makes some sense.
    Thanks in advance,
    Arunesh

    Hi Lalit,
    Did some head breaking with the function module - BAPI_IDOC_INPUT1 to check whether it is calling the EXIT_SAPLMV02_002 internally. Couldn't get anywhere.
    On question of another EXIT in BAPI_IDOC_INPUT1, I don't see any. I am not very proficient in ABAP code, I must say though.
    I found the list of exits from google, almost same list everywhere.
    http://www.sapfans.com/forums/viewtopic.php?f=21&t=296637
    here I got the EXIT, I am talking about.
    Any other way to find either the EXIT or link the above?
    -- Arunesh

  • Problem in creating Purchase order through Idoc

    Hi ABAPers,
    I am trying to post PO document through WE19 t-code using inbound function module BAPI_IDOC_INPUT1 which is calling BAPI_PO_CREATE1 internally.And i am getting below error messages.
    1. Characteristic  does not exist in operating concern AC01
    2. This function only possible for subcontracting items
    3. No instance of object type PurchaseOrder has been created. External reference
    passing data to IDOC:PORDCR102
    Header Segment : E1BPMEPOHEADER and E1BPMEPOHEADERX
    company code    0814
    doc_type            NB
    vendor                0000400001
    poprg-                EPRO
    pgroup               U01
    Item Segment : E1BPMEPOITEM and E1BPMEPOITEMX
    Item                  00010
    material             000000000000000263
    plant                 0374
    Qty                   22.000
    Delivery Segment E1BPMEPOSCHEDULE and E1BPMEPOSCHEDULEX
    Item                  00010
    Schedule line     0001
    delivery date      01.12.2008
    Qty                   22.000
    Note: i am able to create PO successfully, through SE37 by using FM BAPI_PO_CREATE1  with given above data.
    Please confirm me, what else i need to pass to post PO through WE19 t-code using inbound function module BAPI_IDOC_INPUT1.
    Please reply me ASAP.
    Thanks and Regards,
    Sekhar Raju.

    must be data format issue. when you use Function_module/BAPI from SAP GUI, convertion exit is applied automatically. hence data is converted to proper format & submited.

  • Create PO using Idoc with free goods

    Hi guys,
    i'am currently working on a projekt i need to create a purchase order containing free goods.
    We've already tested the PORDCR/PORDCR1 message and Idoc types PORDCR101/102 with BAPI's
    IDOC_INPUT_PORDCR1  - w/ self-defined process code (via we42)
    BAPI_IDOC_INPUT1        - w/ standard process code (BAPI)
    Nothing worked. Got lots of errors in we05 transaction (mostly status 51)
    Important:
    We need to give the Idoc the free gods flag so we didnt need to set the net_price.
    Thanks for your help guys,
    Daniel

    Use Order PORDCR102, with your extension say ZPORDCR102.
    Create one control table and assign Function module to that table.
    Set this new Ztable with all required data like free goods.
    Then create new idoc, this new idoc will take message PORDCR102 and extension will pick new table and add free goods flag while creating PO.
    Hope this helps

  • Problem with goods receipt posting - edi

    Hello,
      Iam using MBGMCR/MBGMCR02 BAPI_IDOC_INPUT1 for posting some goods movements.
    Through the same idoc i will be receiving a returns order number and the item details.With that i need to post the GR for the returns delivery posting the stock in returns.
    How can i automate this process when i use the sales order no and the movement type as 915 it errors out saying  goods receipt not posssible for 915 iam using mvt code '05'
    also i could not find a stock type indicator for returns stock...
    can any one help...
    thanks
    larry

    Better you check with SD Functional consultant . the error message clearly said that. "good Reciept not possible with movement type 915"

  • IDOC reading in ABAP

    Hey,
    found a lot of threads to this issue. Just want to know if I understood correctly.
    I created an own IDOC and the communication from XI to SAP system works.
    Until now I've got a dummy implementation as process code, which I want to
    implement correctly.
    Following steps I would do:
    - Use same interface structure as BAPI_IDOC_INPUT1 as process code/function module
    - in source code calling function module IDOC_READ_COMPLETELY to read the idoc data in internal tables
    - loop on internal tables to deal with IDOC data
    - after successful editing the data, set IDOC_status
    Is this what I have to do? Is the usage of IDOC_READ_COMPLETELY the way you
    would do it?
    thanks
    chris
    Edited by: Christian Riekenberg on Jul 11, 2008 10:32 AM

    Can you please post the SAP example. I have a requirement to see what all went across in an IDOC and compare them with the time entries in SAP system. I can see what went across in a particular IDOC in tcode WE05, but I want that all to be seen by a program as to compare with what we have on the SAP system.
    Please do post that SAP example that helped you.
    Thanks a lot.

  • LSMW CRMXIF_ORDER_SAVE_M02

    Hi
    I try to load sales orders in CRM via LSMW - IDOC. I use message type CRMXIF_ORDER_SAVE_M, basic type CRMXIF_ORDER_SAVE_M02 (also i tried CRMXIF_ORDER_SAVE_M01 and CRMXIF_ORDER_SAVE_U01. What is the difference between these basic types? And which one i have to use???). I've done IDOC inbound processing settings and settigs in LSMW. When i start IDOC GEneration CRM system create the IDOC. The IDOCs created remains with status 64. Then i Start IDoc Processing and CRM system process the IDOC. The IDOCs processed change the status to 51 (incorrect)  - message "Function module not allowed: BAPI_IDOC_INPUT1".  Sometimes IDOCs processed change the status to 62, but in this case i still have no sales order in the system!
    What i might do wrong???
    Help me please!!!!
    Thanks in advance.
    Alex.

    Hi Aleksandr,
    The CRMXIF_ORDER_SAVE_M01 IDOC has a complex structure CRMXIF_BUSTRANS From which the IDOC is generated. This contains two segments CUSTOMER_H and CUSTOMER_I. These are represented by structures CRMXIF_CUSTOMER_H and CRMXIF_CUSTOMER_I. In General the recommendation is to use these structures for Customer specific enhancements.
    refer notes 1022699.
    This should solve the problem.
    Please reward points.
    regards,
    Muralidhar Prasad.C

  • Problem with updating email fields thru  ADRMAS idoc

    Hi
    I have a ABAP program which calls the function module to create a vendor -ERP_IDOC_INPUT_CREDITOR'.
    During the creation of the vendor i can update the adress and telephone numbers but i cant input the email address .
    To solve this i am calling the function module (BAPI_IDOC_INPUT1-function module used in ADRMAS idoc).
    When i run the idoc it updates the field but when i call the Bapi in the abap program  it does not update the data that i have entered  in the function module .
    I tried doing a BAPI_TRANSACTION_COMMIT but it still does not update it.
    Any suggestions  to solve it.
    Also at the end of submitting the idoc it gives me a message
    BAPI SAVEREPLICA has been called successfully
    Is that what adrmas should be giving .
    Thanks

    Hi ,
    Check your BAPI Returen Parameters,  if it successfull then goto ADRC,ADR2,ADR6 tables and check your entry...
    email address in ADR6 table

  • No backend PO in ECC5?

    Hi Gurus,
    Please can someone shed some light on the following error.
    We have activated extended classic scen in srm 5.0, but our srm PO does not replicate over to ECC5 as a display only doc. The checks our basis team have undertaken are:
    i. No idocs are visible in WE05
    ii. errors are displayed in RZ20 say: (a) IDOC comms error: 'error sending IDoc to FI/CO backend for PO3xxxxxxxx, (b) Comm error checking account assignment for PO3xxxxxxxx in system
    iii. the trans type and doc no's are consistent in srm.
    iv. no entries in srm table REQREF
    Any input would be appreciated
    Thank you,
    Mikey
    Edited by: Mike Pallister on Aug 26, 2008 10:07 PM

    Hi Muthu,
    Thank you for the hint. I can now sucessfully get an outboubnd IDOC from our SRM system, however, the Inbound IDOC fails in R/3 with the message. Please can you elaborate what function module should be used for message type BBPCO01 as I am using Process Code 'BAPI' in R/3 transaction code WE20.
    Thanking you,
    M.
    Function module not allowed: BAPI_IDOC_INPUT1
    Message no. B1252
    Diagnosis
    The function module BAPI_IDOC_INPUT1 and the application object type which were determined are not valid for this IDoc.
    Procedure
    1. Please check that the process code in the inbound partner profile is correct.
    2. If this is the case, you should check the ALE inbound methods ALE inbound methods for the process code and see whether the specified function module and application object type are correct.
    3. If this is also the case, then the function module and the application object type are not permitted for the logical message type, message variant, message function and basis type that are contained in the IDoc control record. You should check whether the correct values have been assigned to these fields in the control record. If they do have the correct values, then the assignment to the function module and the application object type needs to be maintained.

  • Which enhancement to use change purchase order quantity ?

    Hi all,
    can u tell me
    1) what is the enhancement to use to change the purchase order quantity with reference to the change in production order   quantity?
    Regards,
    Naveen
    Moderator Message: SEARCH!
    Edited by: kishan P on Nov 29, 2010 11:09 AM

    Hello,
    In this case you should use the message PORDCH and BAPI method BAPI_PO_CHANGE but only exist as of release 4.7.
    Function module    BAPI_IDOC_INPUT1
    Idoc Type              PORDCH01
    Message Type      PORDCH
    So check carefully the following OSS notes:
      [Notes 589066 - BAPI_PO_CHANGE: Incorrect account assignment to network |https://service.sap.com/sap/support/notes/589066] (not be fooled by the description)
    [ Notes 197958 - BAPIs for purchase orders - Missing Functions|https://service.sap.com/sap/support/notes/197958]
    Regards,
    Andrea
    Edited by: Andrea Olivieri on Sep 3, 2009 10:17 AM

Maybe you are looking for