BAPI / IDOC - production confirmation - at lot level

Hi,
    What is the BAPI / IDOC for the production confirmation? Are there different bapi / idocs available for repetitive manufacturing and discrete manufacturing? If anyone knows, please let me know. thanks,
Regards,
Sundar.

Check this BAPI_PRODORDCONF_CREATE_TT
Thanks,
SKJ

Similar Messages

  • Bapi For Production Confirmation ?

    Hi,
    I am using "BAPI_PRODORDCONF_CREATE_TT" for production confirmation.
    I need to also pass the corresponding goods movement for the order operation. How to achieve this. and also what are the mandatory fields to be supplied for good movement.
    Regards,
    Navneeth K.

    Hi Bothra,
    Follow the sample code.
    DATA : BEGIN OF TIMETICKETS OCCURS 0.
            INCLUDE STRUCTURE BAPI_PP_TIMETICKET.
    DATA : END OF TIMETICKETS.
    DATA : BEGIN OF GOODSMOVEMENTS OCCURS 0.
         INCLUDE STRUCTURE BAPI2017_GM_ITEM_CREATE.
    DATA :END OF GOODSMOVEMENTS.
    *DATA : LINK_CONF_GOODSMOV TYPE     BAPI_LINK_CONF_GOODSMOV.
    DATA : DETAIL_RETURN     TYPE     BAPI_CORU_RETURN OCCURS 0 WITH HEADER LINE.
    DATA : RETURN     TYPE     BAPIRET1 OCCURS 0 WITH HEADER LINE.
    DATA : POST_WRONG_ENTRIES LIKE     BAPI_CORU_PARAM-INS_ERR.
    DATA : TESTRUN     LIKE     BAPI_CORU_PARAM-TESTRUN.
    DATA: BEGIN OF LINK OCCURS 0.
    INCLUDE STRUCTURE BAPI_LINK_CONF_GOODSMOV.
    DATA: END OF LINK.
    DATA: BEGIN OF PROPOSE OCCURS 0.
    INCLUDE STRUCTURE BAPI_PP_CONF_PROP.
    DATA: END OF PROPOSE.
    DATA : BEGIN OF LINK_CONF_GOODSMOV OCCURS 0.
    INCLUDE STRUCTURE BAPI_LINK_CONF_GOODSMOV.
    DATA : END OF LINK_CONF_GOODSMOV.
    LOOP AT TIMETKT.
    MOVE-CORRESPONDING TIMETKT TO TIMETICKETS.
    APPEND TIMETICKETS.
    LOOP AT BAPI_ITAB1 WHERE SRL = TIMETKT-SRL.
        MOVE-CORRESPONDING BAPI_ITAB1 TO GOODSMOVEMENTS.
    CONF_QUAN_UNIT.
    CONF_ACTI_UNIT1.
        APPEND GOODSMOVEMENTS.
    ENDLOOP.
    PROPOSE-QUANTITY = 'X'.
    PROPOSE-ACTIVITY = 'X'.
    PROPOSE-DATE_AND_TIME = 'X'.
    PROPOSE-GOODSMOVEMENT = 'X'.
    APPEND PROPOSE.
        CALL FUNCTION 'BAPI_PRODORDCONF_GET_TT_PROP'
         EXPORTING
           PROPOSE                  = PROPOSE
        IMPORTING
          RETURN                   =
          TABLES
            TIMETICKETS              = TIMETICKETS
           GOODSMOVEMENTS           = GOODSMOVEMENTS
           LINK_CONF_GOODSMOV       = LINK_CONF_GOODSMOV
           DETAIL_RETURN            = DETAIL_RETURN.
        CALL FUNCTION 'BAPI_PRODORDCONF_CREATE_TT'
         EXPORTING
           POST_WRONG_ENTRIES       = '0'
          TESTRUN                  =
         IMPORTING
           RETURN                   = RETURN
          TABLES
            TIMETICKETS              = TIMETICKETS
           GOODSMOVEMENTS           = GOODSMOVEMENTS
       LINK_CONF_GOODSMOV       = LINK_conf_goodsmov
        DETAIL_RETURN            = DETAIL_RETURN.
        if return-id is initial.
        commit work.
        endif.
    I think it will be helpfull to u.
    Regards
    Srimanta

  • BAPI/FM for Confirmation of Production order at operation level

    Hi ABAPers,
    I am using the 'BAPI_PRODORDCONF_CREATE_ACT'for Confirmation of Production order at operation level.
    I am able to pass the Production order number and Active Operation get the confirmation done.
    But the Confirmed Qty is not being updating in AFKO table.
    The 'BAPI_PRODORDCONF_CREATE_HDR' cannot be used for Confirmation of Production order at operation level as there is no Operation/Activity(Vornr) field in the input table. Hence using this bapi confirmation of Prod order can be only at Order level.
    Can someone know any FM/BAPI which can be used for the Confirmation of Production order at operation level(not order level).
    Thanks in Advance
    Ramesh Babu Cikka

    Hi Ramesh,
    Please use FUNCTION 'BAPI_PRODORDCONF_CREATE_TT'.
    This will work as like as T/Code "CO11".
    I hope this will help you.
    Example :
      CALL FUNCTION 'BAPI_PRODORDCONF_CREATE_TT'
        EXPORTING
          POST_WRONG_ENTRIES = '0'
          TESTRUN            = ' '
        IMPORTING
          RETURN             = ZRETURN
        TABLES
          TIMETICKETS        = ZBAPI_PP_TIMETICKET
          DETAIL_RETURN      = ZBAPI_CORU_RETURN.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          WAIT = 'W'.
    Lanka

  • FM/BAPI to update Production Order at Operation Level

    Hi Friends,
    Can any one help me in this issue.
    My rek is, needs to update Production Order Sequence Number(AFVC-CY_SEQNRV) at operation level.
    There are some Production Orders under one Project.User is updating theSequence Numberfor the first order in that group (TCode CO02),at the time of save remaining Orders in that group needs to be updated with the same Sequence Number.
    Please provide me with FM/BAPI(operation level not at header level)
    Points Rewarded,
    Thanks in advance,
    PRBode.

    Prathap,
    Have you tried using the Bapi :  BAPI_PP_TIMETICKET
    This would confirm at operation level..
    Hope it is useful.
    Regards
    Ram

  • 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

  • Restrict Authorization at Material level during production confirmation

    Hi SAP Gurus,
    I would like to ask if its possible to restrict authorization at Material Level during production confirmation.
    Our scenario is we have SFG and FG which are handled by different group of people but it has the same Order Type. Now we want to restrict authorization such as one department can only confirm SFG and the other department can confirm FG only.
    Is it possible to set authorization at material type or production scheduler level. IF not possible, is there other way except creation of new Order Type?
    Thanks,
    Raymond

    Hi Raymond,
    DO you mean I should create a customized table for this?
    Yes
    Are there no standard way?
    As per my knowledge, you can control through production order type, so you need to create seprate order type for this
    Thanks,
    Sankaran

  • Business Object (BAPI/IDOC) for production Order

    Hi All
    I have requirement where data is coming from legacy system to R/3 via XI to generate a production order. I am not able to get right BAPI/ IDOC for inbound Production Order. Can anyone has done similar scenario. Can u suggest me BAPI or IDOC for same. I am using IS-Mills 4.7 version for R/3
    Thanx in advance
    Regards
    Vinod

    HI Vinod,
    I think U can use IDOC <b>LOIPRO01</b> for Production Order...
    Regards,
    Sridhar Reddy

  • How to see Production(confirmed) quantity in Capacity leveling view

    Hi,
           I have some quantity with Production(confirmed).I am able to see that in Planning book.But not able to see that in Capacity leveling view.How to see that?
    Thanks&Regards
    Venkadesh

    Anybody any help
    Thanks&Regards
    Venkadesh

  • BAPI, IDOC, ALE, RFC

    Hi friends,
    I am new in BAPI IDOC ALE
    I want to learn these Topics but i dont have any clue or material about this.
    Kindly help me to learn this topics, please give me material and basic clue for this,
    Many Thanks
    Jahnavee Trivedi

    Hi,
    ALE AND IDOC:
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    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
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    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
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    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
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    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
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    There are two filtering in IDoc.
    Segment Filtering:
    Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
    Data Filtering:
    Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
    Please check this link for more information.
    http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
    BAPI MATERIAL:
    please check this:
    http://help.sap.com/saphelp_nw04/helpdata/en/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm
    BAPI Programming Guide
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    BAPI User Guide
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    BAPI is also a Remote enabled function module but the difference between BAPI and RFC is in BAPI there is a bussiness object attached to it which calls SAP application internally.
    BAPI stands for Business Application Programming Interface.
    It is a library of functions that are released to the public
    as an interface into an existing SAP system from an external system.
    http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    Checkout !!
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://techrepublic.com.com/5100-6329-1051160.html#
    http://www.sap-img.com/bapi.htm
    http://www.sap-img.com/abap/bapi-conventions.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    RFC:
    Remote Function Call:
    RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.
    RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.
    RFCs manage the communication process, parameter transfer and error handling.
    Have a look at this link.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
    Regards,
    SHIva(reward if helpful)

  • Manual Creation of Production(confirmed) in Planning book

    Hi Experts,
    I just want to ask if in case I manually enter a production order quantity for a certain material location in Production(Confirmed) key figure, would it automatically populate dependent demand quantity on components?
    I understand that if production order comes from SAP R/3 and CIF to APO, I will have both production order and dependent demand in palnnign book. But in case production order is loaded from an external file or manually entered, would it also gives me dependent demand? Thanks.
    Regards,
    Mylene

    Hi Mylene,
    I agree with Virender (who seems right quite often actually )
    I think you are approaching this the wrong way: you cannot create a SNP production confirm; and will never be able to...
    However, you can create a produciton confirm order via interface; and , providing you do that properly, your order will be visible in SNP, both in produciton confirm and dependant demand.
    I hope it make sense.
    Where you need to concentrate your effort is on this interface.
    You will probalby need interface to create PDS / PPM and to create comfirm order.
    I am not an expert here, but I guess the best is to use bapi (e.g  "PrdDataStructureAPS" (BUS10014) or "ProdProcessModelAPS" (BUS10003 / "ManufactOrderAPS" (BUS10503)
    Thnaks and Regards
    Julien

  • How to retrieve material document no. based on production confirmation no.

    Hi Friends,
    I am retreiving the production confirmation number(PRTNR) thru bapi BAPI_REPMANCONF_CREATE_MTS. Based on that confirmation number I need to retrieve material document number (MBLNR)
    Because multiple users can post finished goods from different locations at same time, I have to complusory retrieve the material document number based on confirmation number only. Tables MKPF and MSEG doesn't have confirmation number fields in them.
    I would appreciate if anyone could suggest me good ideas.
    Thanks in Advance.

    Hi Melih,
    Thank you for your valuable response.
    My BLPP table gets updated with material document as well as confirmation number.
    When I test my FM directly, I get a confirmation number in my export. I don't get a material document number in my export parameter. But, BLPP gets updated with material document number as well as confirmation number.
    But, if I debugg the FM with the same data I get the material document number as well as conf. no. populated in my export parameters.
    This is what I have done:
    Export parameters
    MAT_DOC type BELNR_D
    CONF type PRTNR
    DATA: GS_BLPP               LIKE BLPP,
                          GV_MAT_DOC      TYPE BELNR_D.
    CLEAR: GV_MAT_DOC, GS_BLPP.
        SELECT SINGLE *  INTO GS_BLPP
                         FROM BLPP
                        WHERE PRTNR = CONF
                          AND PRTPS = '0001'.
        GV_MAT_DOC = L_BLPP-BELNR.
        MAT_DOC              = GV_MAT_DOC.
    Please let me know if I have done something wrong.
    Thanks.

  • BAPI for Production Order creation ?

    Hi Experts,
    I am new to PP module and as per my requirement I have to:
    1. Create Production order in ECC 6.0
        After searching BAPI explorer, SDN and other sites I could see that there is no BAPI for Create Production order.
        In one of the link I could find FM CLOI_CHANGES_UPL_31 used to create Production order in SAP.
    Is there any BAPI to create ??
    Can anyone let mw know right FM or BAPI to create Production order with an example.
    2. And I have to:
    Delete Production order
    which BAPI is used for deletion of Prd Ord
    BAPI_PRODORD_SET_DEL_INDICATOR or BAPI_PRODORD_SET_DELETION_FLAG
    For Confirm Production order - in ECC 6.0 Let mw know the BAPI for this ..
    Really helpful if you answer my queries...
    Thanks
    Uday

    Hi udaya,
    use the BAPI 'BAPI_PRODORD_CREATE'
    The following BAPIs are available confirmation of production orders:
        Entry
            Time ticket
            ProdOrdConfirmation.CreateTimeTicketMultiple
            BAPI_PRODORDCONF_CREATE_TT
            Time event
            ProdOrdConfirmation.CreateAtHeaderLevelMultiple
            BAPI_PRODORDCONF_CREATE_HDR
            Order confirmation
            ProdOrdConfirmation.CreateAtHeaderLevelMultiple
            BAPI_PRODORDCONF_CREATE_HDR
            Activity confirmation
            ProdOrdConfirmation.CreateActConfMultiple
            BAPI_PRODORDCONF_CREATE_ACT
        Defaults
            Time ticket
            ProdOrdConfirmation.GetTimeTicketProposal
            BAPI_PRODORDCONF_GET_TT_PROP
            Time event
            ProdOrdConfirmation.GetTimeEventProposal
            BAPI_PRODORDCONF_GET_TE_PROP
            Order confirmation
            ProdOrdConfirmation.GetAtHeaderLevelProposal
            BAPI_PRODORDCONF_GET_HDR_PROP
        Cancelling confirmations
        ProdOrdConfirmation.Cancel
        BAPI_PRODORDCONF_CANCEL
        List of confirmations
        ProdOrdConfirmation.GetList
        BAPI_PRODORDCONF_GETLIST
        Detail data for confirmations
        ProdOrdConfirmation.GetDetail
        BAPI_PRODORDCONF_GETDETAIL
        Existence check
        ProdOrdConfirmation.ExistenceCheck
        BAPI_PRODORDCONF_EXIST_CHK
    Regards,
    Ravi

  • WITH LSMW USING BATCH INPUT/DIRECT INPUT/BAPI/IDOCS

    IN WHAT SCENARIOS CAN WE USE BATCH INPUT/DIRECT INPUT/BAPI/IDOCS WITH LSMW.WHICH IS THE BEST ONE.PLEASE TELL ME THE SCENARIOS OF USAGE.

    It really depends on what you are doing.  There are a lot of "standard" LSMW objects for different business objects, for example, there is a std object for Creating Material Masters, in this case, it is a direct input program. So, the best choice here would be to use the standard program which has been provided, it just so happens that it is a direct input program.  Creating Bill of Materials is another one, but this one is a batch input program, so you have no choice but to go with that.  Of course if there is a BAPI for your business object that would be the next best thing, if a standard object does not exists.
    REgards,
    Rich Heilman

  • Production Confirmation cancellation issue

    Dear All,
    After Production Confirmation (101), stock is in QM and Insp Lot Status is REL. Still System is not allowing CO13 as well as CO11 with 102/262, saying "Change the inspection stock of <material> in QM only".
    Inspection Type: 04, 05 is activated for both Produced Material (101) and consumed material (261). We tried by removing 05 inspection type for both Materials.
    Above error message appeared for Producted Material (101).
    Ideally, System should allow to cancel Production Confirmation when stock is in QM with REL status.
    Request to guide what went wrong.
    Regards,
    Tanuj Parikh

    Dear All,
    Issue solved as per Note: 48815.
    Regards,

  • Production confirmation cancel through QM

    Dear Sir/Mam
    In our scenario when production order is confirmed we get inspection lot with inspection lot origin 04,if material is accepted i post the stock in unrestricted which acceptable by the user,but if the material has to be rejected we do not want put the stock in blocked.We required that if material is rejected its production confirmation should be reversed means its last operation should be cancalled that means mvt type 102.Please guide
    regards
    kunal

    Dear Sir
    Function module done and assigned to Follow up action of Manual and even assigned to catalog 3 in inspection lot orgin 04 in that rejected(R) selected and that follow up is assigned.
    In qa32 when i m going to usage decision selecting 04, R-Rejected I can see follow up action but Function module is not triggered and where the stock to posted should it to be remained in quality.Can this function module can used for the lot whose stock is posted to unrestricted.Awaiting for your valuable answer.
    Please go through  below code
    Let me know the changes if any.
    FUNCTION ZQM_BAPI_PROD_ORDER.
    ""Local Interface:
    *"  IMPORTING
    *"     VALUE(I_QALS) LIKE  QALS STRUCTURE  QALS OPTIONAL
    *"     VALUE(I_QAVE) LIKE  QAVE STRUCTURE  QAVE OPTIONAL
    *"     VALUE(I_QAPO) TYPE  QAPO OPTIONAL
    *"  EXPORTING
    *"     VALUE(E_SUBRC) LIKE  SY-SUBRC
    *"  TABLES
    *"      E_PROTOCOL STRUCTURE  RQEVP OPTIONAL
    *"  EXCEPTIONS
    *"      NOT_FOUND
    *"      INVALID
    **"     REFERENCE(PRUEFLOS) TYPE  QPLOS
    *"     REFERENCE(I_QALS) LIKE  QALS STRUCTURE  QALS OPTIONAL
    *"     REFERENCE(I_QAVE) LIKE  QAVE STRUCTURE  QAVE OPTIONAL
    *"     REFERENCE(I_QAPO) TYPE  QAPO OPTIONAL
    *"  EXPORTING
    *"     VALUE(E_SUBRC) LIKE  SY-SUBRC
    *"  TABLES
    *"      E_PROTOCOL STRUCTURE  RQEVP OPTIONAL
    *"  EXCEPTIONS
    *"      NOT_FOUND
    *"      INVALID
      DATA : CONFIR LIKE  BAPI_PP_CONF_KEY-CONF_NO,
             CONFCOU LIKE  BAPI_PP_CONF_KEY-CONF_CNT,
             RETURN LIKE  BAPIRET1 ,
             LOCKED LIKE  BAPI_CORU_PARAM-LOCKED,
             CREATED_CONF_NO LIKE  BAPI_PP_CONF_KEY-CONF_NO,
             CREATED_CONF_COUNT LIKE  BAPI_PP_CONF_KEY-CONF_CNT.
      DATA:   P_RUECK TYPE AFRC-RUECK,
              P_RMZHL TYPE AFRC-RMZHL.
      DATA: BEGIN OF IT_QALS OCCURS 0.
              INCLUDE STRUCTURE QALS.
      DATA END OF IT_QALS.
      DATA: BEGIN OF IT_AFRC OCCURS 0,
              AUFNR TYPE AFRC-AUFNR,
              RUECK TYPE AFRC-RUECK,
              RMZHL TYPE AFRC-RMZHL,
            END OF IT_AFRC.
    break abap-core.
    *START-OF-SELECTION.
      SELECT single  *
        FROM QALS
        INTO IT_QALS
       WHERE PRUEFLOS = I_QALS-PRUEFLOS.
      IF IT_QALS[] IS NOT INITIAL.
        SELECT AUFNR
               RUECK
               RMZHL
          FROM AFRC
          INTO TABLE IT_AFRC
          FOR ALL ENTRIES IN IT_QALS
          WHERE AUFNR = IT_QALS-AUFNR.
      ENDIF.
      READ TABLE IT_AFRC INDEX 1.
      MOVE : IT_AFRC-RUECK TO P_RUECK,
             IT_AFRC-RMZHL TO P_RMZHL.
      IF SY-SUBRC NE 0.
        MESSAGE 'Value Not Found' TYPE 'I'.
      ENDIF.
      CALL FUNCTION 'BAPI_PRODORDCONF_CANCEL'
        EXPORTING
          CONFIRMATION              = P_RUECK "CONFIR
          CONFIRMATIONCOUNTER       = P_RMZHL "CONFCOU
      POSTG_DATE                =
      CONF_TEXT                 =
       IMPORTING
         RETURN                    =  RETURN
         LOCKED                    =  LOCKED
         CREATED_CONF_NO           =  CREATED_CONF_NO
         CREATED_CONF_COUNT        =  CREATED_CONF_COUNT .
      COMMIT WORK.
      IF SY-SUBRC EQ 0.
        WRITE 'PO Canceled'.
      ENDIF.
    ENDFUNCTION.
    regards,
    Kunal.

Maybe you are looking for