ORDRSP idoc user exit exit_sapleinm_007

i have problem with inbound EDI for po acknowledgment(855) ,message type used ordrsp process code ORDR and basic type is orders05 and function idoc_input_ordrsp
Vendor is sending only vendor material number (IDTNR) and qualifier 002 is used. During IDOC processing I am using user exit exit_sapleinm_007 to get the SAP material number based on Purchase order number.
In user exit I am trying to collect the SAP number based on vendor number (IDTNR)and purchase order from EKPO table
When processing the segment E1EDP19 using the exit_sapleinm_007, I am unable to pass the PO number (EBELN) and therefore I am unable to extract the corresponding SAP number (Customer Number), which resulted in failure of IDOC.
IDOC error message : Material number differs from the ordered material number.
Purchase order (EBELN) is present in segment E1EDP02 and this segment is processed before E1EDP19.
I am not sure how this can be resolved? Is their any other user exit that can be used for ORDRSP idoc in extracting SAP number (customer material number) from vendor material number (IDTNR)

Hi Ashutosh,
All the exits for listed are too early in the flow for you to know if the DN was created successfully or not, like Christian has suggested you will have to use the customer exits/BAIDs available within "GN_DELIVERY_CREATE" to achieve your requirement. There seem to be a couple of customer function exits available, and a BADI - SHP_BADI_GN_DELIVERY_CREATE try them.
Also calling an FM in update task wouldn't help you, unless you have some key information with which you can check if the DN was successfully created.
Regards,
Chen

Similar Messages

Inbound IDOC user exits

Re: IDOC User Exits
Posted: Aug 1, 2006 10:43 AM        Reply      E-mail this post
Hi
I have a basic doubt. We can modify or add new segments and change existing values to segments only for outbound idoc.
I have a requirement where a particular field in a segment would be empty for an inbound idoc. Is it possible to change inbound idoc values after the idoc is created and before it gets posted.
Please let me know,
Regards,
B.Anandh

Updating IDoc data in segments.
STEP 1 - Open document to edit
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
       EXPORTING
            document_number               = t_docnum
       IMPORTING
            idoc_control                  = itab_edidc
       TABLES
            idoc_data                     = itab_edidd
       EXCEPTIONS
            document_foreign_lock         = 1
            document_not_exist            = 2
            document_not_open             = 3
            status_is_unable_for_changing = 4
            OTHERS                        = 5.
STEP 2 - Loop at itab_edidd and change data
LOOP AT itab_edidd WHERE segnam = 'E1EDKA1'.
e1edka1 = itab_edidd-sdata.
IF e1edka1-parvw = 'LF'.
    e1edka1-partn = t_eikto.
    itab_edidd-sdata = e1edka1.
    MODIFY itab_edidd.
    EXIT.
ENDIF.
ENDLOOP.
STEP 3 - Change data segments
CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
           TABLES
                idoc_changed_data_range = itab_edidd
           EXCEPTIONS
                idoc_not_open           = 1
                data_record_not_exist   = 2
                OTHERS                  = 3.

Doubt in Idoc user exit..............

Hi All,
 i have written the user exit for Sales Order subscreen tab called additional data2 , this tab is provided by sap for developer can write their own user exit coding.
 my doubt is whenever PO comes as an Inbound IDOC i need to pass the value from segment to my user exit fields.
 where can i find the inbound idoc user exit for SO .
 Thanks in advance,
Regards,
Saravanan.

Look at enhancement VEDA0001. It has got quite a few user exits you can use. You will also need to enhance the IDOC for the additional fields you have added on your screen.
Cheers,
Sanjeev

Idoc User Exit

Hi Friends,
How do you find the IDOC User exits?
How to create IDOC Custom segment?
Please Let Me know.Any help is Appreciated.
Thanks,
Rinky

How do you find the IDOC User exits?
-->>There is nothing separately you can figure out only IDoc user-exits..Goto particular Transaction code -->system --> status..Click in the program & find out the Exits which is relevent to IDoc..Even u can put a break-point in all exits & find when its called...
How to create IDOC Custom segment?
--> Goto Tcode WE31 to create segments..
Check these links for more details on IDoc's:
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
Hope this helps
* Reward each helpful answer
Raja T

BAPI,BADI ,BDC,ALE ,IDOC,USER EXIT,VALIDATION AND SMART FORMS.

Dear Experts,
I am pretty new in BAPI,BADI ,BDC,ALE ,IDOC,USER EXIT,VALIDATION AND SMART FORMS.
Pls let me know for these topics shall i put the question in this community or should i put in any other form. Pl suggest me .
Regards
Shivas

Plz SEARCH in SCN before posting ,you will get lot of posts .
Don't use all caps in the subject line

Any of the Benefits idoc user exit

Hi All,
I am looking for the any benefit idoc user exit. We neeed to extend BENEFIT3 idoc, i was able to extend the idoc but dont see any user exit where i can def. my def segment.
Not sure how it is working in other case.
Does anybody has any idea as of how to proceed on this.
Appreciate your help in advance.
Thank you,

This thread is vague and does not specify what the ultimate solution was. We were trying to accomplish the same thing - an enhancement to BENEFIT3 IDoc, but were unable to find a suitable user exit. So we put in an OSS note and received the following response:
"...currently there is no user exit/Badi in SAP Benefits Administration
to enhance IDoc BENEFIT3. Such functionality is indeed missing in the
system, which means that you will need to submit a development
request to enhance the system in this respect in a future release."
We are going to try to resolve our problem with a custom infotype.
Anke

Developing custom IDOC , USER Exit , BADI , BAPI and RFC

Hi,
I want basic information on developing custom IDOC , USER exit , BADI ,BAPI and RFC.
Thanks in advance

Neha,
>custom IDOC ,
http://www.geocities.com/xplosion78/customised_ALE_IDOC_BY_SACHIN_DABHADE.zip
>USER exit
USER EXIT
> BADI
BADI Development Contents
> BAPI and RFC
Re: BAPI Development
Cheers
Agasthuri Doss

Which option to choose:idoc user exit or copy standard idoc?

Hi gurus,
We are using idoc technolody to implement the interface between R3 and 3rd party system.
Most of idocs are inbound processing, and it seems standard idoc can't meet our all requirements.
So we are considering the option:i choose doc user exit or create new idoc by copying standard idoc.
Which way do you like better?What are the advantages and disadvantages of them?
Any help will be appreciated.
BTW, our customer will upgrade their R3 4.7 system to ECC6.0 after this project the next year.

Hi,
By making changes in the User-Exits, if you can achieve what you are looking for then I would recommend to use user-exits. SAP programs are not bug free and SAP keeps on updating them by releasing hundreds of notes every day. If customer is upgrading to new version in near future then using standard programs are the best option.
Cheers,

EDI - IDoc - User Exit - Code - Problem - Help - Wanted

Hi EDI Experts,
I have extended ORDERS05 IDOC twice.
ZVKSEG1 is the the segment under extended idoc ZVKORDRS05. This is for one partner.
Z1DATESH01 is the segment under extended idoc Z1ORDER05. This is for another partner.
I have completed the configuration thing in WE82 for both the extensions.
Now the requirement is, whenever a PO is created for the first partner - 100290, the IDoc generated should contain the extra segment ZVKSEG1 and whenever PO is created for the second partner - 10099,the Idoc generated should contain the extrasegment Z1DATESH01.
Using WE20, i have added the extended IDoc type in both the partner profiles under ORDERS message type.
Now i've written the user exit for this using EXIT_SAPLEINM_002.
tables: edidc.
data: z_edidd like edidd occurs 0 with header line.
data: y1dath01 like z1datesh01.
data: yvkseg1 like zvkseg1.
if edidc-rcvprn = '10099'.
z_edidd[] = int_edidd[].
loop at z_edidd.
if z_edidd-segnam = 'E1EDK01'.
read table z_edidd with key segnam = 'Z1DATESH01'.
if sy-subrc <> 0.
y1dath01-DELDATE = sy-datum.
clear z_edidd.
z_Edidd-sdata = y1dath01.
z_Edidd-segnam = 'Z1DATESH01'.
append z_edidd.
endif.
endif.
endloop.
int_edidd[] = z_edidd[].
elseif edidc-rcvprn = '100290'.
z_edidd[] = int_edidd[].
loop at z_edidd.
if z_edidd-segnam = 'E1EDK01'.
read table z_edidd with key segnam = 'ZVKSEG1'.
if sy-subrc <> 0.
yvkseg1-name1 = 'ZVK Chemicals'.
clear z_edidd.
z_Edidd-sdata = yvkseg1.
z_Edidd-segnam = 'ZVKSEG1'.
append z_edidd.
endif.
endif.
endloop.
int_edidd[] = z_edidd[].
endif.
Could you please go through the code and tell me where did i go wrong. The extra segments are not being created for both the partners.
I created PO using ME21n once for each vendor.
Please help me out guys.
Thanks,
Matt

I myself fixed this problem. I made use of XLFA1-LIFNR to manipulate the partner numbers.
Thanks

Inbound IDOC User Exit ZXVEDU04 change IDoc Data

Hi all,
We have to develop an user exit for changing the Plant, Shipping Point and Storage location
We have identified the exit ZXVEDU04 . Is there some other exit for this ??
But which internal table we are supposed to change this to change the data .
If possible send me a sample code
Thanks in Advance .
Vivek K ..

Hi all,
I have done this for a single line item IDoc .
How do i go for IDocs with more than one line item ???
I have hardcoded VBAP-WERKS(1) etc for Plant, Strg Loc and shp pt .
How to identify how many line items are there in the IDocs ??
Thanks in Advance .
Vivek K ..

Debugging inbound idoc user exit

Hi all,
I have a client who wishes to do some data validation when creating an inbound idoc. We've identified the appropriate user exit and set a break-point in it, but how do I get the inbound process to stop here so I can see the data coming through, particularly since the process is initiated from a source external to R/3.
The file data is coming from a warehouse management system into XI, and then being passed from XI through to the function IDOC_INPUT_DELVRY.
Cheers,
Stephen

go thru the below information.
IDOCs:
- IDOC is an Intermediate Document'. It is simply a data container used to exchange information
between any two processes that can understand the syntax and semantics of the data.
An IDOC is created as a result of executing an Outbound ALE or EDI process.
In an inbound ALE or EDI process, an IDOC serves as input to create an application document.
-When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.
This number is unique with in the client.
- IDOCs are independent of the sending and receiving systems.
- IDOCs are independent of the direction of data exchange.
- In the IDOCs, data is stored in text format.
- IDOC will wait until the Remote System is Active.
*IDOC Definition Components
- Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
basic IDOC type or a customer developed basic IDOC type.
- A basic IDOC type has the following characteristics:
Name : A basic Idoc type can be assigned upto a thirty character name.
List of permitted segments: The segments make up the IDOC structure.
Hierarchy of segments : The hierarchy of segments specifies the physical sequence and
any parent - child relationship in the segments.
Mandatory Vs Optional Segments : When used in the IDOC type, each segment has
an attribute that defines whether the segment is option or mandatory.
Minimum/Maximum range for each segment: It defines the maximum and minimum
number of timesa data record corresponding to a segment cn exist in an IDOC.
- Segments : A segment defines the format and structure of a data record.
Segments are reusable componets. A segment consists of various fields that represent data
in data record.
IDOC Run time components:
- A unique IDOC number 16 digits is allocated.
- One control record is attached to the IDOC.
- Segments translate into data records.
- Status records are attached.
- Sytax rules are checked.
IDOC Record Types:
1. Control Record : The control record contains all of the control information about an IDOC,
this information basically includes the IDOC number, sender and receiver information,
and information such as the message type it represents and the IDOC type.
- there is only one control record per IDOC.
- The stucture of the control record is the same for all the IDOCs and is defined by SAP.
- The structure of the control record is defined by the data dictionary structure EDI_DC40.
- The control record is stored in the EDIDC table.
2. Data Record : Data records contain the application data. A data record has two sections
Administrative Section and a Data section.
- The Administrative section cotain the segment name, client, IDOC number, segment number,
hierarchy level information.
- The Data section of a data record is a stram of 1000 bytes where the actual data resides.
- The data record is defined by the data dictionary structure EDI_DD40.
- Data records for IDOCs stored in the EDID4 table.
3. Status Record : Status records are attaced to an IDOC throughout the process as
the IDOC achieves different milestones or encounters an error. At every milestone a statu code,
date and time are assigned.
- Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for
inbound processes.
Message Type: Identifies what type of information transformed between logical systems or partners.
Message type is not a local object type , it is transportable.
Port : A Port defines the medium in which data is exchanged between the two systems in
the ALE process, IDocs are transferred via memory.
1. TRFC ports are used for ALE communicaion.
2. File Ports used by EDI
3. CPI-C ports used to communicate with R/2 systems.
4. Internet ports used to connect with Internet Applications.
5. ABAP-PI ports used to process data via the ABAP programming interface.
6. XML ports used to process files in XML format.
Partner Profiles:
A partner profile has three views, which maintain different parameters for the partner.
1. The General Parameters View : Values are stored in table EDPP1.
2. The Outbound Parameters view : Values are stored in table EDP13, except for the
Message control parameter , which are stored in table EDP12.
3. The Inbound Parameters View: Values are stored in table EDP21.
Transaction Codes :
WE31- Segment Creation
WE30 - IDOC structure
WE81 - Message type creation
WE82 - Link between Message type and IDOC type.
WE21 - Creation of POrt
WE20 - Partner Profile creation
WE19 - Test tool for IDOC Processing.
SALE - ALE (Application Linking and Enabling) settings
Go through the link for basics related to IDOCs:
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6cdd507d11d18ee90000e8366fc2/plain.htm
Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
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
You need to excahnge data between systems you need an interface as medium for data transfer.
IDoc also treat one of the interface options for data transfer.
Check this link
http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
IDOC Debugging:
1) We generally go for customized IDocs if none of the SAP standard IDoc does not suit our need/business process. Creating is custom IDoc should be a very stringent process. The SAP standard IDocs should be rigorously checked (if any user exits can be of our help or IDoc extension will solve the purpose).
2) WE19 is the test tool by which we can create IDocs to see whether our functionality is working. It is mostly used to debug inbound function modules.
For outbound function module debugging you can use the following:
1) RBDMIDOC - for master IDocs configured via change pointers.
2) RSNASTED - for transaction IDocs with output/message control.
3) RSEOUT00 - For IDoc whose status is "to be processed".

Bapi,idoc,user exits

hi, im learner i want to need some idea in user exits,bapi,idoc any body having documents on above topics plz to send me...............plz

Check these links..
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
New to enhancements
creation of table in ecc6
for Function module exits
New to ABAP Enhancements
For menu Exits and screen exit
USER EXIT
Search through www.enips.com.
You can find lot of material there.
BADI's
http://help.sap.com/saphelp_erp2005/helpdata/en/73/7e7941601b1d09e10000000a155106/frameset.htm
http://support.sas.com/rnd/papers/sugi30/SAP.ppt
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/abapindx.htm
http://members.aol.com/_ht_a/skarkada/sap/
http://www.ct-software.com/reportpool_frame.htm
http://www.saphelp.com/SAP_Technical.htm
http://www.kabai.com/abaps/q.htm
http://www.guidancetech.com/people/holland/sap/abap/
http://www.planetsap.com/download_abap_programs.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
/people/thomas.weiss/blog/2006/04/03/how-to-define-a-new-badi-within-the-enhancement-framework--part-3-of-the-series
/people/thomas.weiss/blog/2006/04/18/how-to-implement-a-badi-and-how-to-use-a-filter--part-4-of-the-series-on-the-new-enhancement-framework
User Exits
http://www.erpgenie.com/sap/abap/code/abap26.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
TO find all BADI's
Follow the below steps to find out what all BADI's are called when you press any button in any transaction.
1) Goto se24 (Display class cl_exithandler)
2) Double click on the method GET_INSTANCE.
3) Put a break point at Line no.25 (CASE sy-subrc).
Now
4) Execute SAP standard transaction
5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.
6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.
7) This way you will find all the BADIs called on click of any button in any transaction.
A. BAdI Definition
1. SE18
2. Enter the name for the BAdI to be created in customer namespace and press "Create".
3. Enter a definition for your BAdI and on the interface tab enter a name for the BAdI interface. SAP proposes a name and it is pretty good. Meanwhile a BAdI class is also created which is not in our concern.
e.g for "ZTEST", SAP proposes "ZIF_EX_TEST" for the interface and "ZCL_EX_TEST" for the class.
4. Save your BAdI.
5. Double-click on the interface name. It will pass to a Class Builder session to make you implement your interface. If you are not familiar to the Class Builder; it's a bit like Function Builder and it will be easy to discover its procedure.
6. Save and activate your interface.
B. Calling your BAdI from an application program
1. Declare a reference variable with reference to the Business Add-In interface.
e.g. DATA exit_ref TYPE REF TO zif_ex_test.
2. Call the static method GET_INSTANCE of the service class CL_EXITHANDLER. This returns an instance of the required object.
e.g.
CALL METHOD CL_EXITHANDLER=>GET_INSTANCE
CHANGING instance = exit_ref .
3. After those two steps, you can now call all of the methods of the BAdI where it is required in your program. Make sure you specify the method interfaces correctly.
C. BAdI Implementations
1. SE19
2. Enter the name for the BAdI implementation to be created in customer namespace and press "Create".
3. It will request the BAdI definition name to which this implementation will be tied.
4. Enter a definition for your implementation and on the interface tab enter a name for the implementing class. Again SAP proposes a name and it is pretty good.
e.g for "ZIMPTEST", SAP proposes "ZCL_IM_IMPTEST".
5. Save your implementation.
6. To implement a method, just double-click on the method name and you will be taken to the Class Builder to write the code for it. Here you redefine the BAdI interface methods.
7. You must activate your implementation to make it executable. You can only activate or deactivate an implementation in its original system without modification. The activation or deactivation must be transported into subsequent systems
Regards,
Balaji Reddy G
***Rewards if answers are helpful

IDOC User Exits

Hi,
I have two customer function in the basic type WMIVID01.
FM: L_IDOC_INPUT_WMINVE.
I need to populate one value ivnum into the segment E1LINVX at runtime.
Can anyone let me know how to do the same. The user exits found are.....
001 and 003.
When i checked inside, some ZX.. includes are there. Which one of them should i use for inserting values.
Please also note that there is only one segment E1LINVX present in WMIVID01.

Hi
I have a basic doubt. We can modify or add new segments and change existing values to segments only for outbound idoc.
I have a requirement where a particular field in a segment would be empty for an inbound idoc. Is it possible to change inbound idoc values after the idoc is created.
Please let me know,

Inbound IDoc user exit

I am attempting to write my first user exit for an Inbound IDoc. Outbound seems easy by comparison. I am going to add a date to VBAK-MAHDT from and extended ORDERS03 segment. My extended segment is pretty much like E1EDK03.
I'm working with enhancement VEDA0001. For include ZXVEDU03 of component EXIT_SAPLVEDA_001 I have this so far:
DATA:
w_z1edk03 LIKE z1edk03,
w_vbak LIKE vbak.
CASE segment-segnam.
WHEN 'Z1EDK03'.
    IF segment-sdata(3) = 'Z01'.
      w_z1edk03 = segment-sdata.
      MOVE dxvbak TO w_vbak.
      w_vbak-mahdt = w_z1edk03-datum.
      MOVE w_vbak TO dxvbak.
    ENDIF.
WHEN OTHERS.
ENDCASE.
Am I on the right track? Isn't there something else that I need for include ZXVEDU04 of EXIT_SAPLVEDA_002?

I went ahead and added:
IF contrl-mestyp = 'ORDERS' AND
contrl-idoctp = 'Z_EK_ORDERS03'.
for that check Mahendra.
I am trying to figure out how to update dxbdcdata correctly to add my data to the screen in EXIT_SAPLVEDA_002 include ZXVEDU04. With the debugger I see updates in dxbdcdata for screens '4002' and '4003' but not for '4001' where I believe my data should be added. Do I just append the records for '4001' myself and does it matter what order it is in?

OREDRS IDoc User exit

Hi Experts,
we have a the below requirement for creating sales order using ORDERS05 IDoc
If   ../E1EDP01/E1EDP19/QUALF = 002
        If u2026/E1EDP01/E1EDP19/IDTNR = 'DEL-0123456'
        Then
          Drop the respective.../E1EDP01 segment
Please let me know how to achieve this in the user exit(SAP enhancement VEDA0001).
Thanks in advance,
MK

hi experts,
I need to enhance FM u201CIDOC_INPUT_ORDERSu201D. So I had created the new project ZDEV_VEDA via tcode CMOD and under this new project, I assigned the VEDA0001 enhancement. I wanted to enhance Function exit EXIT_SAPLVEDA_001 (INCLUDE ZXVEDU03). But I had encountered this message:
Program names ZX... are reserved for includes of exit function groups. Message no. DS027
Any ideas what is this about? Appreciate so much.
TQ.

ORDRSP idoc user exit exit_sapleinm_007

Similar Messages

Maybe you are looking for