Exit in iw31 for generating IORDER IDOC

Hi,
We are trying to generate the IORDER01 IDoc for PM orders through transaction iw31. I need exit name where i can write code for generating idoc. Exit should be triggered <b>after save</b> as i need to pass the following data - order id and operation details.
I tried exit - FUNCTION EXIT_SAPLCOIH_016 but it doesnt work
""Lokale Schnittstelle:
*"       IMPORTING
*"             VALUE(CAUFVD_IMP) LIKE CAUFVD STRUCTURE CAUFVD
*"             VALUE(AFVGD_IMP) LIKE AFVGD STRUCTURE AFVGD
*"             VALUE(ACTYP) LIKE TC10-TRTYP
INCLUDE ZXWOCU13.
ENDFUNCTION.
Please suggest correct exit name. Thanks in advance.
Sonali

Thanks Sajan.
Exit 031 triggers after save but at that point the order id(aufnr) is not generated. The system generated order number is also to be passed to the idoc so i need exit after FM - CO_ZV_ORDER_POST (include LCOIHF2V) is triggered.
i could not find exit after this FM. Apart from exit can we use any other method ? i've not worked on badi so not sure which method of IWO1_ORDER_BADI would work.
Any help on this is appreciated. Thanks a lot.
Sonali

Similar Messages

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

Generating the IDocs for some particular segments only......

Hi Gurus,
I have activates the change Pointers for generating the IDocs whenever the master dtaa is changed.
Is there any technique so that I can recive the IDocs containing only those segment's data which is relevant for me.
Abhi....

The question I have asked is not related to Inbound I Docs processing.
Actually I am sending the IDocs to Non-SAP system whenever any change is made to the master data, using the Change Pointers.
Now, the situation is that the file that is getting generated contains the data corresponding to many segments. So, is it possible to restrict the segments/fields for which the data is generated.
Thanks In Advance.......
Abhi.,,

How do i generate the idoc for the custom infotype?

Hi Experts,
I have a requirement to create the custom infotype and generate the idoc for the custom infotype
whenever the user change or crate the data by PA30, PA40 transaction .
so please give some help to write a logic for generate the idoc?
Thanks in advance.
Venkat

I have just found out from the Archives, it is not possible to generate a formula line (trend line) in Numbers_08.
I am currently upgrading to Numbers_09.

Standard program for creating outbound IDoc holding wbs+cost plan

Hello,
a)
Before we start developing our own ABAP, I would like to ask the forum if somebody knows if there is already a standard ABAP program for generating outbound IDocs including wbs-element data (CJ20N; wbs ID, description) plus annual data from the cost planning (CJ41; such as fiscal year and costing items from unit costing; quantity, unit, price per unit, total price, description of item) ?
b) we are planning to use the logical message /ISDFPS/PS, basic type /ISDFPS/PS01 and enhance this IDoc with segments for the costing items from the cost planning.
Question: Do you know if there is a standard IDoc which has segments for both wbs-element data and costing items?
Kind regards
Viveka Schwartz

Hi Frank,
Did u check this Link on the PP confirmaitos[LINK|http://help.sap.com/saphelp_47x200/helpdata/en/12/3bbc1c504811d182c20000e829fbfe/frameset.htm]
Reg
Dsk
Edited by: DSk on Sep 14, 2010 3:44 PM

Standard program for creating outbound IDoc including wbs + cost planning

Hello,
a)
Before we start developing our own ABAP, I would like to ask the forum if somebody knows if there is already a standard ABAP program for generating outbound IDocs including wbs-element data (CJ20N; wbs ID, description) plus annual data from the cost planning (CJ41; such as fiscal year and costing items from unit costing; quantity, unit, price per unit, total price, description of item) ?
b) we are planning to use the logical message /ISDFPS/PS, basic type /ISDFPS/PS01 and enhance this IDoc with segments for the costing items from the cost planning.
Question: Do you know if there is a standard IDoc which has segments for both wbs-element data and costing items?
Kind regards
Viveka Schwartz

Hi Frank,
Did u check this Link on the PP confirmaitos[LINK|http://help.sap.com/saphelp_47x200/helpdata/en/12/3bbc1c504811d182c20000e829fbfe/frameset.htm]
Reg
Dsk
Edited by: DSk on Sep 14, 2010 3:44 PM

User exit / BADI for the MATQM01 IDOC type?

Hello,
I am working on a Material Master conversion that will need to include the Material Inspection Setup. Using BD10 to send the material 'In Full' generates these MATQM01 IDOCs successfully. As part of this conversion I need to map some old plants to new plants.
Is there a user exit or BADI within the MATQM process that I can use to accomplish this?
The BADI/Exits for BD10 do not access the MATQM data. There are no exits listed for QL11 which is the standalone code for creating MATQM idocs.
Any help would be appreciated!
John

Thank you guys for the replies. I will try the Rules and Filters approach to implement the logic I require. If the logic is too complex then I will go with the z-copy of QL11.
Thanks!

Is it possible to generate outbound idocs for FI invoices? How?

Is it possible to generate Outbound idocs for FI invoices? How? or else i have to write program to get data in file and pass it to translator. Please help.

Dear Gabriel
Before letting you know the possibility, can you please let me know why you want such a requirement, since standard has not provided such copy control, to my knowledge.
As you would know order type KB is for consignment fillup where you are just transferring the goods from FG unrestricted to your own warehouse and that is why in standard you can see the copy control KB --> F8 which means you can raise proforma against delivery and not against fillup order.
So think of whether really you wanted to raise proforma against fillup order which is NOT recommended by SAP. However, still if you feel that the requirement is so to have, you can make the settings in VTFA.
thanks
G. Lakshmipathi

Function Module to Generate Outbound IDOC for Sales Documents

Hello Experts,
Can someone please help me, I need to know which function module to use in order to generate the outbound IDOC for sales documents. Some of the fm's I have come across are the following:
IDOC_OUTPUT_ORDERS, but actually for Purchase Orders
IDOC_OUTPUT_ORDRSP, but did not generate any IDocs for my sample Sales Order.
Points will be given for any help provided.
Thanks in advance.

Hi Nagaraj,
I tried using the IDOC_OUTPUT_ORDERS but I keep getting an error that the Purchase Order <xxx> does not exist, even though the document I tried is a sales order. For everyone's reference here is the code:
form process_data.
DATA v_idoc       TYPE edidc-docnum.
DATA i_edidd      TYPE TABLE OF edidd.
DATA wa_idoc_ctrl TYPE edidc.
LOOP AT i_nast INTO wa_nast.
    CLEAR i_msgs[].
    CALL FUNCTION 'WFMC_PROTOCOL_GET'
      EXPORTING
        cps_nast        = wa_nast
      tables
        messages        = i_msgs
     EXCEPTIONS
       NOT_FOUND       = 1
       OTHERS          = 2.
    LOOP AT i_msgs INTO wa_msgs WHERE arbgb EQ 'E0'.
*--- Check first if there is an IDOC
      IF wa_msgs-msgv1 IS INITIAL.
        CONTINUE.
      ENDIF.
      v_idoc = wa_msgs-msgv1.
      CLEAR i_edidd[].
      CLEAR wa_idoc_ctrl.
      CALL FUNCTION 'IDOC_READ_COMPLETELY'
        EXPORTING
          document_number                = v_idoc
        IMPORTING
          IDOC_CONTROL                   = wa_idoc_ctrl
*         NUMBER_OF_DATA_RECORDS         =
*         NUMBER_OF_STATUS_RECORDS       =
        TABLES
*         INT_EDIDS                      =
          INT_EDIDD                      = i_edidd
        EXCEPTIONS
*         DOCUMENT_NOT_EXIST             = 1
*         DOCUMENT_NUMBER_INVALID        = 2
          OTHERS                         = 3.
      CALL FUNCTION 'IDOC_OUTPUT_ORDERS'
        EXPORTING
          object                              = wa_nast
          control_record_in                   = wa_idoc_ctrl
*       IMPORTING
*         OBJECT_TYPE                         =
*         CONTROL_RECORD_OUT                  =
        tables
          int_edidd                           = i_edidd
*       EXCEPTIONS
*         ERROR_MESSAGE_RECEIVED              = 1
*         DATA_NOT_RELEVANT_FOR_SENDING       = 2
*         OTHERS                              = 3
      IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      COMMIT WORK.
    ENDLOOP.
ENDLOOP.

Message type for generating IDOC for SUBCONTRACTING PURCHASE ORDER

Hi All,
I have to generate IDOC for PO creation or change .
I am using IDOC_OUTPUT_ORDERS and IDOC_OUTPUT_ORDCHG.
The messagetype.idoctype I am using is ORDERS. ORDERS05 and ORDCHG. ORDERS05.
Now the confusion is regarding whether this message type will work in case of SUBCONTRACTING PURCHASE ORDER as well ?
As I have gone through some websites and came to know that I will have to use PORDCR1.PORDCR102 specially for subcontracting.
And programs we need to use is BUS2012_ICH_R3 instead of RSNASTED and Form Routine SEND_PORDCR1 instead of EDI_PROCESSING.
Purchase Order Collaboration scenario - Not generating IDOC in ECC
http://www.erpgenie.com/faq/edi_purchasing.htm on this site question no 8.
Subcontract PO IDOCs
I hope your experience will help me .
Please reply ASAP.
Edited by: uttam27 on Dec 4, 2011 1:47 PM

There is a generic function to create change pointers for all message typs - 'CHANGE_POINTERS_CREATE_DIRECT'. This is triggered only if you configure your message type to create change pointers from BD50.
Once you activate it do any change to orders you can see change pointer tables BDCPV filled. Then BD21 will read the changes and generated outbound idocs accordingly.

Inbound IDOC error (Name MARA is not in the namespace for generated BW Metaobjects)

Hi everybody,
we are currently having some issues with importing idocs into our ERP DEV System and i cannot figure out what the problem could be.
I am trying to import an IDOC Type ARTMAS (5) but i keep getting the following error "Name MARA is not in the namespace for generated BW Metaobjects"
The system is a ERP only system with no BI content activated at all.
I don´t find any more errors nor any dumps or SLG1 entries related to this issue.
Did someone already experienced that kind of problem, or do some of you maybe have an idea where to have a deeper look.
thanks & best regards
Peter
EDIT:
Running on ERP 6.0 EHP 7 SPS 4

Hi Ganesh,
I guess there is something wrong with the data in the ODS.
Check this post:
Re: error 18 in the update!
Bye
Dinesh

Generating an IDOC for each Order present in the file (File to IDOC)

Hi ,
I have a requirement where in i have to generate an idoc for each orders present in a file . Initially i had implemented 1:N mapping by changing the occurence of idoc to 1..unbounded & using it as external definition i was able to generate multiple idocs.
But now the requirement is that even if one record contains invalid data , then XI shoul process remaining records(which has valid data) & then raise an alert for the invalid record . I have implemented this approach by using BPM (splitting the message) & the sending out each record as a single message to (1:1 mapping between file & IDOC).
But now they dont want me to use an BPM . They want me to come up with an approach using 1:N mapping only where in i can make sure that the mappig doesnt fail even if there is one invalid record ,they want me to process remaining records & raise an alert for the invalid one .
As far as i know this cant be done without BPM . Please let me know any valuable suggestions or inputs if there is any
Regards
Vinay P.

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

Generate outbound idoc for Customer Master

Hi Developers,
I have requirement to generate outbound IDOC for Customer Master Data. I need to send customer master data through an Outbound IDOC. Can we generate an outbound DEBMAS06 idoc? Can someone help me finding a solution to this problem?
Thanks in advance for helping.
Regards,
Gajendra

Hi,
If you have done all the required settings (logical system, partner profiles, distribution model), then either transaction BD10 / BD14 will help you generate the IDOC.
If you want to send the idocs automatically, then you will to configure some program.
Unlike transaction data, Master data IDOCS are not triggered immediately, you will have to do the required configuration in SPRO.
Transaction SPRO
SAP Customizing Implementation Guide -->
SAP Web application Server --> Application Link Enabling --> Modeling and Implementing Business Processes -->
Master Data distribution --> Replication of Modified Data --> Creating IDOCS from Change Pointers
Take a look at this thread.
Re: automatic Idoc outbound
Regards,
Ravi
Note : Please mark the helpful answers
Message was edited by: Ravikumar Allampallam

Workitem is not generating for an Inbound Idoc

Hi All,
The problem I am facing, when inbound idoc is processing in SAP, if there are any errors occurred, it would generate a work item and that will be sent to user Inbox (SBWP) as per the workflow. Here it is not generating a work item for an inbound idoc where is there is an error. So user is not receiving work item mail to inbox, to check about the idoc error. This idoc has been processed through the function module.
Could you please let us know your input on this issue.

Hi Hitu,
The problem could be at multiple places.
To debug check the workflow which sends the workitem to the user when an error occurs.
Check if this workflow is getting triggered when the error occurs. If yes, then check the step whre this workflow fails.
Else, check the event linkage of this workflow and check if the associated event is getting triggered or not. If yes, check if the event linakge is active for the workflow.
There could be other places as well to diagnose the error.
Check if these inputs gives you some direction.
Regards,
Saumya

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

Exit in iw31 for generating IORDER IDOC

Similar Messages

Maybe you are looking for