ECC6 Super Session Chains - Standard Inbound IDoc/BAPI

I am trying to setup supersession chains in ECC6 environment. Is there a BAPI/standard Inbound Idoc for creating/updating these?
Also, is there an standard outbound IDoc if I want to syndicate these chains to other SAP Systems?
Please note that I am not implementing APO,

Similar Messages

  • What is the standard inbound idoc for substation management?

    Hello Experts,
    Can anybody help me to find out the standard inbound idoc for substation management?
    The following field are requied to be  filled in idoc.
    1)Power_Produced(STAGR)
    2) Reduction_Power_Consumed(STAGR)
    3)Ancillary_Power_Consumed (STAGR)
    4)Unit (MEINB)
    5) UOM and Date (BUDAT)
    If possible please tell me the standard BAPI for these fileds.
    Thanks in advance for your help.
    Thanks and Regards,
    Suresh.

    Hi Debo,
    What is your exact requirement?
    Are you trying to find the standard configurations available for a webdynpro application? then, use t-code SE15 and open the application name and use the tree structure to find out the available configurations under WD application.
    sample:
    Regards,
    Rama

  • IDOC/BAPI for Production order creation from Legacy system

    Hi all
    We are using an interface to create Production orders from legacy to SAP. Would you recommend an IDOC or a BAPI to create Production orders. If IDOC or BAPI then could you please mention which one?
    thanks a bunch

    Hi John,
    For your purposes, please use BAPI for production order creation from legacy system. There is no standard inbound IDoc available to use. SAP has an IDoc for outbound interface only (message type LOIPRO).
    If there is an inbound IDoc available, I would recommend to use an IDoc.
    IDoc technology has excellent error handling and will allow you to reprocess an error (if any).
    BAPI is also good approach to use and fast in term of  processing.
    For BAPI approach, you can use BAPI BAPI_PRODORD_CREATE.
    Hope this will help.
    Regards,
    Ferry Lianto

  • Inbound Idoc type for Usage Decision QA11

    Dear SAP Gurus,
    Would like to find out if there is any inbound idoc type to perform Usage Decision (transaction QA11).
    Will reward points for any kind of help. Thank you.
    regards,
    Ju Lee

    Hi,
    There is no standard Inbound Idoc for UD. But there is BAPI available for same "BAPI_INSPLOT_SETUSAGEDECISION".

  • Inbound IDOC basic type HRMD_A07: Why no validation available?

    I am using a standard inbound IDOC basic type HRMD_A07 to update employee master data (IT0000 & IT0001). However, i found out that this IDOC just directly updates to the infotypes without any validation. For example, i provide an invalid company code (BUKRS) and personnel area (WERKS), the IDOC still updates into database without any proper validation.  
    Filled the following fields in the IDOC segments:
    E1PLOGI
    plvar=01, otype=P, objid=00000001, opera=I
    E1PITYP
    plvar=01, otype=P, objid=00000001, infty=0000, begda=20120101, endda=99991231
    E1P0000
    pernr=00000001, infty=0000, endda=99991231, begda=20120101, massn=01, massg=01, stat1=3, stat2=3
    E1PITYP
    plvar=01, otype=P, objid=00000001, infty=0001, begda=20120101, endda=99991231
    E1P0001
    pernr=00000001, infty=0001, endda=99991231, begda=20120101, bukrs=XXXX, werks=XXXX, persg=1, persk=EC, abkrs=99, plans=00000111, otype=S
    Please help me out in case I am missing something. Thanks.

    Additional Info:
    In WE21 at the TRFC Port, it is possible to set this Option:
    Send Only Fields of Selected Segment Version
    The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
    But if we are using an reduced message type, all fields of the newest release are in the segement.
    The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
    But it is never called when createing an material IDOC with BD10.
    Bug or feature?
    Kind regards
    Manuel

  • How to Create a Return Order wrt a Standard Order using Inbound IDOC Orders

    HI,
    We have a scenario :
    Standard Order - is exiting in System with 2 line items :
    Item 10
    Qty 20
    Item 20
    Qty 30
    Is it possible create a Return Order With Reference to this standard order for Line Item 20 only using inbound IDOC Orders?
    If yes what should be the mapping in the IDOC about the Standard Order, Item and QTY ?
    Regards
    Anurag

    hi,
    try using this bapi.
    /AFS/BAPI_SALESORD_CREATEFDATA.
    thanks,
    satish

  • Non English characters conversion issue in LSMW BAPI Inbound IDOCs

    Hi Experts,
    We have some fields in customer master LSMW data load program which can
    contain non-English characters. We are facing issues in LSMW BAPI
    method with non-English characters Conversion. LMSW steps read and
    conversion are showing the non-English characters properly with out any
    issue. While creating inbound IDOCs most of the non-English characters
    replaced with '#' and its causing issues in creating customer master data in
    system. In our scenario customer data with non-English characters in
    the first name, last name and address details. Any specific setting
    needs to be done from our side? Please suggest me to resolve this issue.
    Thanks
    Rajesh Yadla

    If your language is a unicode tehn you need to change the options  like IN SAP you need to change it to unicode  in the initial screen Customize local layout(ALT F12) options 118  --> Encoding ....

  • Inbound IDOC FM with BAPI

    Hi Everyone,
    I need some information about posting an application using inbound IDOC with BAPI. I need to write a FM for
    Inbound IDOC with BAPI to post it. Can some one give me direction as where to start as I am new to BAPI.
    Thanks in advance.
    Regards,
    vicky

    Hi Vicky,
    Please take a look at this link which will show step by step on how to setup inbound proscessing.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    Also check this links for sample codes.
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    Hope this will help.
    Regards,
    Ferry Lianto
    Message was edited by: Ferry Lianto

  • Standard IDOC/BAPI to create work order in CRM from ECC PS

    Hello Guys,
    Any input on any standard IDOC/BAPI I could use to create a work order in SAP CRM based on the data feed from SAP ECC (Project systems)?
    Any help on this would be really appreciated.

    Hii.
    Did u get answer of SAP-> XI->CRM. IF so, share wid us.
    I m stuck in same kinda scenario

  • Standard IDoc / BAPI to get Employee Personal Details

    Hi All,
    Is there any Standard IDoc / BAPI to get Employee Personal Details like EMP-ID Name, Address in HR Modules.
    Bye
    Satish Reddy

    check with this: bapi_persdata_getdetailedlist

  • How to create the INBOUND Function Module for INBOUND IDOCs

    Hi Friends,
    Can any Suggest me How to proceed to Create an INBOUND Function Module for Processing the INBOUND IDOCS
    which are recieved from XI Server ?
    I am working in SAP-ISU
    Here i will recieve the INBOUND IDOCs for the Meter Reading Orders.
    We have a Standard INBOUND FUNCTION MODULE
    IDOC_INPUT_ISU_MR_UPLOAD
    which Uploads the Meter Reading Results.
    I copied the Same function Module into ZIDOC_INPUT_
    and working on it.
    Can any one suggest me, whether i am going in correct way or not.
    In IDOC_INPUT_ISU_MR_UPLOAD Inbound fun module,
    BAPI_MTRREADDOC_UPLOAD is used to Update or Insert the Meter Reading Results,
    My requirment is to Insert and Update the Meter Reading Orders which are Inbounded from XI.
    Can I Use the Same BAPI
    BAPI_MTRREADDOC_UPLOAD
    to Update the below fields,
    EABL-SERNR
    EABL-ZWNUMMER
    EABLG-ABLESGR
    EABL-V_ZWSTAND
    EABL-N_ZWSTAND
    EABL-ABLHINW
    EABL-ZSKIPC
    EABL-ADAT
    EABL-ATIMTATS
    EABL-ADATTATS
    EABL-ATIM
    EABL-ZMESSAGE
    EABL-ABLESER(Meter reader number)
    Kindly Suggest me,
    Thanks in Advance,
    Ganesh

    Hello Ganesh
    I think you are going completely astray with you z-function module for IDoc processing.
    If you look at TABLES parameter METERREADINGRESULTS (type BAPIEABLU ) of BAPI_MTRREADDOC_UPLOAD you will find many of the requested fields already:
    EABL-SERNR => BAPIEABLU-SERIALNO
    EABL-ZWNUMMER =>REGISTER
    EABLG-ABLESGR
    EABL-V_ZWSTAND
    EABL-N_ZWSTAND
    EABL-ABLHINW
    EABL-ZSKIPC
    EABL-ADAT
    EABL-ATIMTATS => ACTUALMRTIME
    EABL-ADATTATS => ACTUALMRDATE
    EABL-ATIM
    EABL-ZMESSAGE
    EABL-ABLESER(Meter reader number)
    Field EABL-ZMESSAGE appears to be custom field (at least I cannot find it on ECC 6.0). If this field was added using include CI_EABL then you probably can get these values into the BAPI using the EXTENSIONIN parameter.
    Check routine CHECK_UPLOADRECORDS in the BAPI which allows two extension structures:
    - BAPI_TE_EABL
    - BAPI_TE_EOSB
    Not surprisingly BAPI_TE_EABL contains the include CI_EABL.
    Regards
      Uwe

  • Issue while trying to create Sales Order from Inbound Idoc ORDER05

    Hi All,
    I am trying to create a sales order through an Inbound idoc ORDERS05 created out of a Purchase order. The header pricing conditions from the Purchase orders gets populated in E1EDK05 segment and this needs to go to the Sales order header conditions while trying to create the Sales order.
    But when the fields are getting incorrectly mapped to the Sales order. Issue  being, the segment E1EDK05-BETRG contains the condition value. But this fields gets populated to the KOMV-KWERT (condition value) screen field on the Sales order header conditions. But this should have got mapped to field KOMV-KBETR (Rate). If I look at the Purchase order, E1EDK05-BETRG is the field getting fetched from field KOMV-KBETR on the Purchase order. So this should have correspondingly got mapped to KOMV-KBETR on the Sales order as well.
    This looks like a standard behavior. But if any of you have encountered this issue before please let me know if any Correction instructions are available for the same. If this some issue in Pricing conditions configuration, do let me know.

    Hi Paaavan
    You can set a break-point include "FV45PFAP_VBAP_BEARBEITEN_VORBE" that is called by both the SAP Standard and BAPI where the data is prepared and checked in the internal table XVBAP. Compare both SAP standard VA01 and your 'Z' program for what may be different in XVBAP.
    I think the problem my be with regards to the business_object number that is hardcoded in the standard function module. It has given me issues before and hence I tend to use the function module  SD_SALESDOCUMENT_CREATE to create sales documents with.
    Regards,
    Marius

  • Urgent help required : Batch processing error of an inbound idoc

    hi,
       i have a problem while posting an idoc to the GL(FB01).
    i'm using an Inbound idoc message type : ACC_GL_POSTING
    idoc type : ACC_GL_POSTING01.
    Process code : BAPI.
    In the transaction code OBA7 i have enabled a particular document type as BATCH INPUT ONLY.
    i have set the option " Trigger by background program" in the partner profile (we20).
    while testing the process i'm getting the error "Document type -- is only defined for batch input".
    how can i overcome this error? can idocs be used to post for transaction that are batch enabled . plz help me.
    with regards.
    T.Jeyagopi.

    Jeyagopi,
    There are different types of Data loading into SAP.
    BATCH INPUT / BDC / IDOC / BAPI etc. BATCH INPUT are standard programs that take the data and update SAP. I don't think that is same as batch processing of IDOC.
    You might want to remove the setting of batch input, retain the batch processing in WE20 and try it out.
    In my opinion it should work.
    Regards,
    Ravi
    Note : Please reward points for the posts that help you.

  • Send mail to a specific user group when an Inbound Idoc processing fails

    I am using standard Message type DEBMAS, but the process code is customed (say ZDEBM as the function module is customed). Can you tell me what configurations are required to activate the error notification message to a user when the inbound idoc fails?

    hi,
    i think u need to check tcode swu3 for automatic workflow customizing and check in we40 (error AND STATUS PROCESSING) whether the processing code is assigned to the workflow task.
    if it is assigned,the workflow will be automatically triggered and the mail will be sent to the user by itself.
    ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
    Workflow functions as follows:
    A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
    If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
    If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
    For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
    1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
    2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
    3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
    If an error occurs, the system determines:
    1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
    2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
    3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
    regards,
    pankaj singh

  • Help required in posting inbound idocs

    Hi,
    We are facing a problem during integration testing to post inbound idocs.
    The scenario is :
    A custom FM is written to process the inbound idocs, which does the following processes in sequence.
    1. BAPI used to create Goods Receipt
    2. BDC used to create Delivery using VL01N
    3. BDC used to create Handling Unit using VL02N
    4. BDC used to create Post Goods Issue using VL02N
    The VL01N creates a deivery, and using that delivery BDC calls VL02N to create HU.
    In unit testing the idocs are success, but when multiple idocs are used in integration testing, all fails either during delivery creation or HU creation.
    The error message we often get when HU is failed is  : "Runtime error RAISE_EXCEPTION has occured ".
    We have also incorporated a commit work and wait of 5 seconds after each BDC to avoid locking problem if any.
    The partner profile is set to ' trigger by background program'.
    Standard program RBDAPP01 is scheduled to collect the IDocs in status 64 and then to be processed.
    The package size used is 1,  inorder to process idocs one by one to avoid locking.
    Should any object type be given in RBDAPP01 ?
    If so, is it required to maintain any record for that object type in table TBD55 to process idocs serially in RBDAPP01 ?
    Any help in this regard is appreciated.
    Thanks in advance
    Regards
    Meena George

    Hi,
    We are facing a problem during integration testing to post inbound idocs.
    The scenario is :
    A custom FM is written to process the inbound idocs, which does the following processes in sequence.
    1. BAPI used to create Goods Receipt
    2. BDC used to create Delivery using VL01N
    3. BDC used to create Handling Unit using VL02N
    4. BDC used to create Post Goods Issue using VL02N
    The VL01N creates a deivery, and using that delivery BDC calls VL02N to create HU.
    In unit testing the idocs are success, but when multiple idocs are used in integration testing, all fails either during delivery creation or HU creation.
    The error message we often get when HU is failed is  : "Runtime error RAISE_EXCEPTION has occured ".
    We have also incorporated a commit work and wait of 5 seconds after each BDC to avoid locking problem if any.
    The partner profile is set to ' trigger by background program'.
    Standard program RBDAPP01 is scheduled to collect the IDocs in status 64 and then to be processed.
    The package size used is 1,  inorder to process idocs one by one to avoid locking.
    Should any object type be given in RBDAPP01 ?
    If so, is it required to maintain any record for that object type in table TBD55 to process idocs serially in RBDAPP01 ?
    Any help in this regard is appreciated.
    Thanks in advance
    Regards
    Meena George

Maybe you are looking for