How do I execute IDOC for message type LOIPRO

How is it possible to execute IDOC using message type LOIPRO which I have configured with change pointers?   Change pointers are using object ORDER.
I am looking to only generate IDOC for production order changes / updates that meets the criteria set by the change pointers.  If something in the order changes, but that field is not being looked at by change pointers, I don't need IDOC to pick up that order.
I don't want to have to run RCCLTRAN or RCCLORD on a scheduled job. Only need to have activity if change pointers are activated. Am I going down the wrong road using LOIPRO ?

Hi Bob,
Could you please guide me through the process of creating/triggering a change pointer based LOIPRO? Your help much appreciated.
Tabraiz

Similar Messages

  • Trigger inbound BAPI IDOC for message type ACC_GL_POSTING

    I configured our SAP system for inbound GL postings -- message Type ACC_GL_POSTING process code BAPI.  I successfully tested all the configuration pieces using WE19. 
    So how do I trigger the inbound process from my external non-SAP system.  I would prefer not create a flat file that is passed by calling EDI_DATA_INCOMING.  I also do not want to use BAPI_ACC_GL_POSTING_POST.  So what RFC enable FM can I call to pass data and trigger the IDOC generation and processing?  Is there anything standard?

    I will use the standard RFC enabled function module IDOC_INBOUND_SYNCHRONOUS.  No custom abap development will be needed.
    Message was edited by:
            David F

  • Outbound IDOC for message type PAYEXT

    Hi,
    I am trying to send a IDOC from my SAP system to a EDI vendor. For one particular vendor in segment E1IDKU3 field PAIRZAWE (payment terms) is mot coming, thought this data is been maintained in Vendor Master Data.
    In Segment E1IDKU4 field FCAREGUL is also missing for which also there is a data maintained in Vendor Master.
    Can anybody explain why this is happening.
    Also, which is the FM or IDOC creation-processing program for this message type.
    /Manik

    Hi Manik,
    Your function module to process the IDOC will either be FI_EDI_PAYEXT_PEXR2001_OUT or FI_EDI_REMADV_PEXR2001_OUT depending on whether you are doing a remittance advice or payment advice.
    In include LIEDPF1T, subroutine FORM FILL_SEGMENT_IDKU4 USING DOC_TYPE, you will find the following code. This tells me that your E1IDKU4 problem is also related to your instruction key settings. Check this table and see what is wrong.
          IF NOT T015W IS INITIAL.
            CASE T015W-DTKVS.              "Gebührenregelung
              WHEN '00'.
                E1IDKU4-FCAREGUL = Q_FCA_GETEILT.
              WHEN '01'.
                E1IDKU4-FCAREGUL = Q_FCA_Z_PFICHTIGER.
              WHEN '02'.
                E1IDKU4-FCAREGUL = Q_FCA_Z_EMPFAENGER.
            ENDCASE.
          ENDIF.
    If it helps, please reward and close the thread.
    Srinivas
    Message was edited by: Srinivas Adavi
    By the way what is Sardinians?

  • IDoc for message type WMPIHU (Creating Pick HUs)

    Hi,
    does anyone know the structure of the IDoc for the WMPIHU message type?
    Is specified by the WM-LSR interface but it's not listed into the "Interface Between the WMS and External Systems" document.
    Thanks
    Michele

    IDOC Bais Type is WMPHID01.
    segment type E1LPHUX. you can check the stracture as of your system version in WE31.

  • Generating an IDOC for Message type PROJECT in Change pointer?

    Hi,
    I am trying to generate an IDOC. for the Message Type PROJECT(Actually this msg. type PROJECT is for BAPI method) in CHANGE POINTERS but it is possible Error is coming, is there any other method to use the message type in change pointer technic.
    Thanks,
    Vinayak,
    Message was edited by: vinayaga sundaram

    Hi Vinay,
    Had a similar requirement few days back..
    What we did was to do a multimapping of 1:N where N = N1 and N2, N1 is the Idocs which you are doing today, N2 is the set of invalid records...
    Now we have written this as a file and then created another interface which will pick the file and based on the name of file we decided the To address. We have used mail package and this interface (file to mail ) was made as a generic one so that it can be used across many interfaces...
    filename and To address relationship was maintained as a value mapping in ID... You can have a thought of this approach and try to send the invalid records as a mail rather than alert.
    Regards
    Suraj

  • Process Code for Message Type LOIPRO(in ALE/IDOCS)

    Hi all,
            I have to implement Production order Interface(create Production order,change Production order etc).The requirement is for eg:,I created one production order and posted it;it should get reflected in the recieving system.Does anyone know the process code for LOIPRO.I checked it in we42,WE64 and even the tables TEDE1 and TEDE2.But its not available.Process code and function module is necessary to continue with WE20.
    Thanking you in advance,
    anjaly

    Hi
    it may sound like not good news, but I think the answer is described in OSS Note 198252 - Special features of POI message category LOI*.
    There all LOI* idocs are mentioned and then they say:
    The message categories named are part of the POI (Production Optimization interface) interface.This interface and the message categories contained in it were developed for the transfer to non-R/3 systems.Therefore, an inbound processing in the R/3 system is not planned.The message categories are transferred via separate transactions / reports of the POI interface (Transactions POIM, POIT).Functions which exceed these transactions are not supported.For this reason, the above-mentioned ALE functions cannot be used for the message categories described.
    So, in short, there is no inbound process code for LOIPRO.
    Inbound processing then should be done through self-developed programs / idocs, calling BAPI-s (for example).
    Regards,
    Joe
    Edited by: Joseph Yasman on Jun 30, 2009 1:46 PM

  • IDOC of message type COMCMT

    Hi,
    Does anybody know how to generate a IDOC of message type CODCMT do you have some doc about it?
    Thanks alot
    Regards,
    Zheng
    Edited by: zhengliu on Jun 16, 2009 12:09 PM
    Edited by: zhengliu on Jun 16, 2009 12:10 PM

    Thank you.
    In fact, I have already read that doc, but after the definition of these datas, what i must do?
    For example, are there some data are obligatory?
    Is this IDOC an IDOC outgoing?
    Regards,
    Zheng
    Edited by: zhengliu on Jun 16, 2009 1:21 PM

  • Specific process code for Production order message type LOIPRO

    Hello,
    Is there any specific process code for Production order message type LOIPRO.
    Request you to reply.
    Thanks
    Prashanth

    Hi Prashanth,
    sorry for last thread ... that not contain full information ...
    For message type LOIPRO you can use process code APLI.
    In IDOC PARTNER definition, the partner is linked with an IDOC TYPE and PROCESS CODE for inbound processing. This process code is in turn linked with a FUNCTION MODULE to process the IDoc such as IDOC_INPUT_INVOIC_MRM (Reff..  http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_cid519558,00.html)
    Regards,
    Amit

  • How to create an extension for generated type idoc

    Hi all,
    Can u please look into this
    How to create an extension for generated type idoc ?  for example Idoc type BATMAS02

    Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
    - Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
    - Click on Create new and enter a description and press enter.
    - Click on ZIDOCTYPE01 and then on the Create icon.
    - Enter ZIDOCTYPE as the segment type, click on Segment Editor.
    - Enter a description for your segment type and create.
    - Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
    - Save and generate, press back
    - To release the segment choose Goto, Release from the menu.
    - Check the box on the line of your segment.
    - Save, back and enter.
    - Your Idoc type structure should be displayed with your new segment.
    - Save and back.
    - To release the Idoc type choose Extras, Release type from the menu and Yes.
    ALE FUNCTION MODULE ENHANCEMENTS
    Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
    The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
    • For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
    • From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
    • Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
    Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
    All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
    When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
    • Execute transaction CMOD.
    • Enter name of project, say CSTMAST1.
    • Click on Create.
    • Enter a description of the project.
    • Save.
    • Click on SAP Enhancements.
    • Enter VSV00001 for Enhancement.
    • Save.
    Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
    As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
    The two important factors to consider while developing the customer function are:
    1. The point in the ALE function module where the function exit occurs
    2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
    Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
    Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
    Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
    Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
    • From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
    • Find Customer Function 001.
    • Double-click on 001.
    • The function EXIT_SAPLVV01_001 will be displayed.
    • Double-click on INCLUDE ZXVSVU01.
    • You will be asked to create a new include object. Proceed as desired.
    • Enter code (as in Listing 1).
    • Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
    Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
    To maintain the contact personâs business address of a customer:
    • Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
    • Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
    With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
    Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
    The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
    Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
    regards,
    srinivas

  • LSMW: ALE/IDOC, getting the Create a partner profile for message type

    Hi Gurus,
    In my current project, i need to upload the employee data using the ALE/IDOC method with the LSMW
    when i'm generating the idoc in the 13th step, its posing the information message stating that:
    Create a partner profile for message type 'ZEMP_MSG'
    In partner profile i already assigned the message type .
    How to solve this issue, <inappropriate urgency removed by moderator>
    Thnks&regards,
    sree
    Edited by: Thomas Zloch on May 13, 2011 9:55 AM

    This forum's aim is not only to search for information and ask the members questions, but also to share knowledge. When you have asked a question and found a solution, do share with the rest.

  • Error monitoring through workflow for idoc with message type ORDRSP

    Hi All,
    Through WE19 I am trying to post a failed idoc ie idoc in 51 status for message type ORDRSP to check whether the event IDOCORDRSP-INPUTERROROCCURED event is triggering or not. Though the idoc is going into 51 status and partner profile is maintained I cannot find this event in SWEL. I checked in fm IDOC_INPUT_ORDRSP fm and found that workflow_result is 99999.
    Can anybody tell me why the event is not getting triggered for the message type ORDRSP or where do I debug to find out what is going wrong. IDOC_INPUT_ORDRSP  fm is getting called from BUS2012 'S method confirmfromORDRSP which is very strange.So I am not getting where do I debug.
    Regards
    Suchandra

    Hi All,
    Solved it by my self.. To trigger the event we need to populate the EDIDC control record in WE19 and press standard inbound button 'not test by inbound fm) and then the inputerroroccured event will trigger...
    Regards
    Suchandra

  • How outbound idoc of message type WMMBXY is created? any program or FM name

    Hello Gurus,
    How outbound idoc of message type WMMBXY is created? any program or FM name??
    basic type : WMMBID01... i checked the idoc in my system, it does not have any process code....
    also, i checked the exit : EXIT_SAPLMBMB_001. It has some code but nothing to fill the segments...
    BR,
    Ks

    got the answer in : WMMBXY and WMMBID02

  • How to create outbound IDOC for Accounting document type RV

    Hello All,
    We have a requirement to create a downpayment request for a customer. We have copied the FAZ billing type and created a ZFAZ. For this the accounting document type generated is RV. This RV is a statistical document and does not contain any debits and credit entries. It is just to inform the customer to pay. We have to generate an IDOC for the same. I have configured FIDCC1 standard FI message type for this in ALE. But it does not seem to work.
    Does anyone have any inputs on this ? May be RV does not use the message type FIDCC1 ? Anything in relation to RV or downpaymnts, please let me know..
    Appreciate your responses.
    Thanks
    SH.

    Hello Alpesh,
    I tried adding breakpoints to the following userexits and many other places where they occur..but while creating billing doc FAZ nor while generating accounting document RV they were triggered.
    I have created a distribution model and created the partner profile with outbound for basic type INVOIC02 for message type INVOIC . What do you say?
    Just a note that this is an outbound process and i cannot use process codes.
    - EXIT_SAPLVEDF_001 User_Exit controll data IDoc_Output_Invoic
    - EXIT_SAPLVEDF_002 User_Exit customer enhancement of segments outbound invoice
    Thanks
    Smitha
    Edited by: Smitha H on Jul 25, 2008 7:56 AM

  • 1 request Idocs created for message type MATMAS

    Hi Experts
    I have done necessary config.
    I have attempted BD10 and BD11.
    I have got message that "1 request Idocs created for message type MATMAS"
    But iam unable to find the material in target system.
    Please suggest what need to be done.
    regards
    ramSiva

    Marias,
    And in PI, after having changed the password (why not), have you unlock this user account ? in SU01 of PI, you have a lock button.
    if you did it, and changed also the password, as explained, you have perhaps another (or several) program like a RFC destination which uses another password, and so after some exchanges... with a bad/old password, you have your message "too many...", and then the user is again locked...
    If you change the password in PI, you should change it in all application which uses this user. I hope you have not the same user from ECC to PI, than from a third-party to PI...
    that's why: the use of such technical users have to be referenced in a doc. By this way, if password has to modifiy, we know where we have to update it (mainly in different RFC destination).
    Mickael
    Edited by: Mickael Huchet on Dec 5, 2011 5:33 PM

  • Create a partner profile for message type - 'CRMXIF_ORDER_SAVE_M'

    Hi
    I am trying to create IDOC generateion through LSMW.
    i AM GETTING THE MESSAGEcreate a partner profile for message type - 'CRMXIF_ORDER_SAVE_M'
    How do I create this profile??????

    Hi,
    Execute transaction BD64.
    Identify you distribution Model,
    Select the leaf node, and from menu select
    Environment->Generate Partner Profile
    Here in you specify 'Output mode' and 'Processing Mode'.
    Click on Execute.
    Check if any error occurs (Marked with Red color).
    Try creating the IDOCs
    Best Regards,
    Pratik Patel
    Reward with points if it is of any help to you!

Maybe you are looking for