User Exit-Idoc extension customising
Hello all,
Can anyone tell me how I can establish a Link between a Basic idoc type and Idoc Extension?
I wrote a INCLUDE programme in the USER EXIT SAPLVV01.
I really appreciate your help.
Note: Points for sure.
Thank you
Joslyn-
The link between Basic IDOC type and IDOC extension is done in the partner profile first (WE20). After you have created an extension for your IDOC, you need to provide the same under Extension IDOC type in the outbound parameters of partner profile.
I am not sure about your requirement but from the user exit you are using, I guess you have more than one extension for customer master IDOC and you want to choose one based on certain parameters. The import and tables parameters of this exit should provide you enough information to do the same.
Let us know with specific questions if you need more info.
KK
Similar Messages
-
User Exit IDOC creation - When purchase order gets created
Hi All,
The requirement is whenever user creates a Purchase Order in the current SAP system an IDOC needs to get created and be sent to another SAP system where a Sales Order will be created.
Can anybody suggest the correct User exit/enhancement at the time of Purchase order creation which could be used ?
Also the function modules for creating the IDOCs within the user-exit.
Thanks for your help.Hi Meghna,
Your requirement is SAP standard function which means you don't have to use any user exit.
What you need to do is configure output control, then when a PO saved, a idoc will send to vendor automaticly.
Here is a step brief
1. configure output type in NACE
2. Add condition record in NACE
3. Setup partner profile in WE20
if you need detailed doc, give me your email, I can send you.
Regards,
Brown -
Regarding documentation on User Exits, IDOCS, Interfaces etc.
Hi Friends,
Can any one help me if any documentation on User Exits(MM/WM related), ALE IDOCS/ INTERFACES etc available which shall help in understanding the above concepts.
Quick help will be highly appreciated and rewarded pls.
Thanks in Advance
Regards,
Prasanna.this info is spread though all channels SAP has, but unfortunatly not consistent, thats why it is so hard to find something.
You can find info at help.sap.com
e.g. this link (see the menu on the left as well)
http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/frameset.htm
Further you can find info at SAP MArketplace (OSS notes)
Or directly to the coding in SE37 and SE38.
IDOC and ALE documentation can be found here:
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
and
http://www.logosworld.com/www5/books/IDocBook/IDocBook.htm
Edited by: Jürgen L. on Oct 24, 2008 12:21 PM -
User exit for incoming PO - (PO is created by CIFing TLB order to R/3)
Hi All,
I need to find out the APO INBOUND user exit for reciving the PO information from the connected R/3 system. Initially a TLB order is created in APO and CIFed to APO and after the PO is created in connected R/3 system this PO number and related information is CIFed back to APO and this TLB order is replaced by the R/3 PO number.
Please help me outto gain full points.
Thanks in Advance,
Chandan DubeyHi,
I am not clear with ur query and therefore check out the list of Inbound and outbound Idoc user-exits:
IDoc Inbound User Exits
1. ACC_BILLING
Accounting: Post invoice (OAG: LOAD RECEIVABLE)
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
2. ACC_EMPLOYEE_EXP
FI/CO: HR posting GL (AcctngEmplyeeExenses)
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
3. ACC_EMPLOYEE_PAY
FI/CO: HR posting AP (AcctngEmplyeePaybles)
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
4. ACC_EMPLOYEE_REC
FI/CO: HR posting AR (AcctngEmplyeeRcvbles)
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
5. ACC_GL_POSTING
Accounting: General G/L account posting
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
6. ACC_GOODS_MOVEMENT
Accounting: Post goods movement (OAG: POST JOURNAL)
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
7. ACC_INVOICE_RECEIPT
Accounting: Post invoice receipt (OAG: LOAD PAYABLE)
ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
8. ACLPAY Accounting: Inbound invoice
ACCID001 EXIT_SAPLACC1_031 IDoc ACLPAY: Userexit for creditor in accounting document
ACCID001 EXIT_SAPLACC1_032 IDoc ACLPAY: Userexit for GL posting in accounting document
ACCID001 EXIT_SAPLACC1_033 IDoc ACLPAY: Userexit for taxes in accounting document
9. ACLREC
Accounting: Billing document
ACCID001 EXIT_SAPLACC1_011 IDoc ACLREC: Userexit for debitor in accounting document
ACCID001 EXIT_SAPLACC1_012 IDoc ACLREC: Userexit for GL posting in accounting document
ACCID001 EXIT_SAPLACC1_013 IDoc ACLREC: Userexit for taxes
10. ACPJMM
Posting in accounting from materials management
ACCID001 EXIT_SAPLACC1_021 IDoc ACPJOU: Userexit for GL posting in accounting document
11. ARTMAS
Create and change of material master (Retail)
MGV00003 EXIT_SAPL1001_003 Enhancement for article master: IDoc inbound
12. BLAOCH
Purchasing contract change
MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
13. BLAORD
Purchasing contracts
MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
14. BLAREL
Release order documentation for distributed contracts
MM06E001 EXIT_SAPLEINM_004 Customer enhancements for release documentation inbound
15. COND_A
Conditions: master data for price determination
VKOI0001 EXIT_SAPLVKOI_001 Interchange of Conditions: Inbound Processing Modifications E1KOMG Segment
VKOI0001 EXIT_SAPLVKOI_002 Interchange of Conditions: Inbound Processing Customer Segments
16. CREMAS
Distribute vendor master
VSV00001 EXIT_SAPLKD02_001 Inbound: Read and process vendor segments
17. DEBMAS
Customer master
VSV00001 EXIT_SAPLVV02_001 Inbound: Read and update additional customer master segments
18. DELINS
Delivery schedule/JIT schedule
VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
VED40001 EXIT_SAPLVED4_002 Copying Data to Screens for Incoming EDI Docs
VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
19. DESADV
Delivery: Shipping notification
LMELA010 EXIT_SAPLEINM_010 Customer enhancement shipping notification inbound: line item
MM06E001 EXIT_SAPLEINM_006 Customer enhancements for shipping notification inbound
V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
20. DOCMAS
Master document
CVDS0001 EXIT_SAPLCVALE_001 Userexit for ALEDVS (DOCMAS inbound)
21. DOLMAS
Document-object links
CVDS0001 EXIT_SAPLCVALE_003 Userexit for ALEDVS (DOLMAS inbound)
22. EDLNOT
EDL delivery notes
VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
VED40001 EXIT_SAPLVED4_002 Copying Data to screens for Incoming EDI Docs
VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
23. FIDCC1
Send entire FI documents (user exit 003/4)
F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
F050S002 EXIT_SAPLF050_004 FIDCC1 IDoc inbound: Change IDoc / do not process
F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
24. FIDCC2
Send entire FI documents (user exit 005/6)
F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
F050S003 EXIT_SAPLF050_006 FIDCC2 IDoc inbound: Change IDoc / do not process
F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
25. FIDCMT
Sending single items for FI-GL
F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
26. FINSTA
Bank Statement
FEDI0005 EXIT_SAPLIEDP_201 FI-EDI: inbound - bank statement/ Lockbox - Final processing
FEDI0005 EXIT_SAPLIEDP_202 FI-EDI: inbound - bank statement/ Lockbox - Processing of segments
27. FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
28. GSVERF
Cred. memo procedure
VED50001 EXIT_SAPLVED5_001 User Exit for Condition Value Tolerances in the Self- Billing Procedure
VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
29. HRMD_A
HR: Master data and organizational data (appl. system)
RHALE001 EXIT_SAPLRHA0_002 HR-CA: ALE inbound processing: Export parameter
RHALE001 EXIT_SAPLRHAL_002 HR-CA: ALE inbound processing: Change info type data
RHALE001 EXIT_SAPLRHAL_004 HR-CA: ALE inbound processing: conversion segment/ info type
30. INFREC
Purchasing info record
MMAL0004 EXIT_SAPLMEAI_004 ALE source list distribution: inbound processing userdefined data
MMAL0004 EXIT_SAPLMEAI_003 ALE purchasing info record distribution: inbound processing segments
31. INVOIC
Invoice / Billing document
FEDI0001 EXIT_SAPLIEDI_001 FI-EDI: Invoice receipt - Determine G/L account per invoice line
FEDI0001 EXIT_SAPLIEDI_002 FI-EDI: Invoice receipt - Determine add. acct assignm. per line item
FEDI0001 EXIT_SAPLIEDI_003 FI-EDI: Invoice receipt - Fill the screen field 'Allocation'
FEDI0001 EXIT_SAPLIEDI_004 FI-EDI: Invoice receipt - Determine the segment text
FEDI0001 EXIT_SAPLIEDI_005 FI-EDI: Invoice receipt - Determine the name of the BDC session
FEDI0001 EXIT_SAPLIEDI_011 MM-EDI: Invoice receipt - Determine purchase order item
FEDI0001 EXIT_SAPLIEDI_101 FI-EDI: Invoice receipt INVOIC01 - additional assignment
FEDI0001 EXIT_SAPLIEDI_102 FI-EDI: Invoice receipt INVOIC01 - add data
FEDI0001 EXIT_SAPLIEDI_111 MM-EDI: Invoice receipt INVOIC01 - additional assignment
FEDI0001 EXIT_SAPLIEDI_112 MM-EDI: Invoice receipt INVOIC01 - add data
MRMH0002 EXIT_SAPLMRMH_011 Logistics Invoice Verification:inboud EDI message, company code
MRMH0002 EXIT_SAPLMRMH_012 Logistics Invoice Verification:inboud EDI message, control flags
MRMH0002 EXIT_SAPLMRMH_013 Logistics Invoice Verification:inboud EDI message, assignment
MRMH0002 EXIT_SAPLMRMH_014 Logistics Invoice Verification:inboud EDI message, segments
MRMH0002 EXIT_SAPLMRMH_015 Logistics Invoice Verification:inbound EDI message, before posting
32. LIKOND
Listing conditions
WSOR0001 EXIT_SAPLWSOI_001 Enhancement for assortments: inbound IDoc
33. MATMAS
Material Master
MGV00001 EXIT_SAPLMV02_002 Enhancement for material master IDoc: Update
34. MRESCR
Create reservation
SAPLMEWB EXIT_SAPLMEWB_001 Customer exit for processing of reservations via BAPIs
35. ORDCHG
Purchase order/order change
MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
VEDB0001 EXIT_SAPLVEDB_001 SD EDI incoming change orders: read additional data from IDoc
VEDB0001 EXIT_SAPLVEDB_002 SD EDI incoming change orders: additional data for dynpros
VEDB0001 EXIT_SAPLVEDB_003 SD EDI incoming change orders: further activities after calling
VEDB0001 EXIT_SAPLVEDB_004 SD EDI incoming change orders: closing activities per
VEDB0001 EXIT_SAPLVEDB_005 SD EDI incoming change orders: closing activities by order block
VEDB0001 EXIT_SAPLVEDB_006 SD EDI incoming change orders: setting order type
VEDB0001 EXIT_SAPLVEDB_007 SD EDI incoming change orders: additional checks of IDoc
VEDB0001 EXIT_SAPLVEDB_008 SD EDI incoming change orders: error handling
VEDB0001 EXIT_SAPLVEDB_009 SD EDI incoming change orders: additional checks of IDoc segments
VEDB0001 EXIT_SAPLVEDB_010 SD EDI incoming change orders: manipulation of status ecords
VEDB0001 EXIT_SAPLVEDB_012 SD EDI incoming change orders: change internal table
36. ORDERS
Purchase order / order
MCP20008 EXIT_SAPLMCP2_008 User exit: Processing of purchase order header
MCP20008 EXIT_SAPLMCP2_009 User exit: Processing of purchase order item
37. ORDERS
Purchase order / order
MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
VEDA0001 EXIT_SAPLVEDA_001 SD EDI incoming orders: read additional data from IDoc
VEDA0001 EXIT_SAPLVEDA_002 SD EDI incoming orders: additional data for dynpros
VEDA0001 EXIT_SAPLVEDA_003 SD EDI incoming orders: further activities after calling
VEDA0001 EXIT_SAPLVEDA_004 SD EDI incoming orders: closing activities per order
VEDA0001 EXIT_SAPLVEDA_005 SD EDI incoming orders: closing activities by order block
VEDA0001 EXIT_SAPLVEDA_006 SD EDI incoming orders: setting order type
VEDA0001 EXIT_SAPLVEDA_007 SD EDI incoming orders: number of ordering party
VEDA0001 EXIT_SAPLVEDA_008 SD EDI incoming orders: error handling
VEDA0001 EXIT_SAPLVEDA_009 SD EDI incoming orders: additional checks of IDoc segments
VEDA0001 EXIT_SAPLVEDA_010 SD EDI incoming orders: manipulation of status records
VEDA0001 EXIT_SAPLVEDA_011 SD EDI incoming orders: change internal table
WVFB0001 EXIT_SAPLWVFB_002 Customer exists for store order PO confirmationdata seg.
38. ORDRSP
Purchase order / order confirmation
MM06E001 EXIT_SAPLEINM_005 Customer enhancements for order confirmation inbound
MM06E001 EXIT_SAPLEINM_007 Customer enhancements inbound confirmation: reading
MM06E001 EXIT_SAPLEINM_008 Customer enhancements inbound confirmation: final
WVMI0001 EXIT_SAPLWVMI_003 ORDRSP VMI inbound, modification before creating purchase order
39. PORDCR
Create purchase order
SAPLMEWP EXIT_SAPLMEWP_002 Customer exit for processing of purchase orders via BAPIs
40. PREQCR
Create purchase requisition
SAPLMEWQ EXIT_SAPLMEWQ_001 Customer exit for processing of requisitions via BAPIs
41. PROACT
Stock and sales data
WVMI0001 EXIT_SAPLWVMI_002 IDoc PROACT inbound: prior to processing
42. REMADV
Payment advice
FEDI0002 EXIT_SAPLIEDP_101 FI-EDI: Incoming pmnt advice - Extended allocatn of IDOC -> applicatn data
FEDI0002 EXIT_SAPLIEDP_102 FI-EDI: Incoming pmnt adivce - Closing allocatn of IDOC -> applicatn data
43. REQOTE
Inquiry
VEDQ0001 EXIT_SAPLVEDQ_001 SD EDI inbound inquiry: read additional data from IDoc
VEDQ0001 EXIT_SAPLVEDQ_002 SD EDI inbound inquiry: additional data for dynpros
VEDQ0001 EXIT_SAPLVEDQ_003 SD EDI inbound inquiry: further activities after calling
VEDQ0001 EXIT_SAPLVEDQ_004 SD EDI inbound inquiry: closing activities per inquiry
VEDQ0001 EXIT_SAPLVEDQ_005 SD EDI inbound inquiry: closing activities by inquiry block
VEDQ0001 EXIT_SAPLVEDQ_006 SD EDI inbound inquiry: setting inquiry type
VEDQ0001 EXIT_SAPLVEDQ_007 SD EDI inbound inquiry: number of sold-to party
VEDQ0001 EXIT_SAPLVEDQ_008 SD EDI inbound inquiry: error handling
VEDQ0001 EXIT_SAPLVEDQ_009 SD EDI inbound inquiry: additional checks of IDoc segments
VEDQ0001 EXIT_SAPLVEDQ_010 SD EDI inbound inquiry: manipulation of status records
VEDQ0001 EXIT_SAPLVEDQ_011 SD EDI inbound inquiry: change internal table
44. SBINV
Credit memo procedure with invoice creation
VED50001 EXIT_SAPLVED5_002 User Exit for messages in the Self-Billing Procedure SBINV
VED50001 EXIT_SAPLVED5_003 User Exit for Tolerances in the Self- Billing Procedure SBINV
VED50001 EXIT_SAPLVED5_004 Customer-Function for changing invoice data SBINV
VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
45. SDPACK
Packing confirmation
VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
VMDE0004 EXIT_SAPLVMDE_004 Shipping Interface: Message SDPACK (Packing, Inbound)
46. SDPICK
Picking confirmation
VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
VMDE0003 EXIT_SAPLVMDE_003 Shipping Interface: Message SDPICK (Picking, Receipt)
47. SHP_IBDLV_CONFIRM_DECENTRAL
Confirmation (Inbound Delivery)
V50B0001 EXIT_SAPLV50I_002 User exit for BAPI Verification of Inbound Deliveries
48. SHP_IBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
V50B0001 EXIT_SAPLV50I_001 User exit for BAPI Duplication of Inbound Deliveries
49. SHP_OBDLV_CONFIRM_DECENTRAL
Confirmation (Customer Delivery)
V50B0001 EXIT_SAPLV50I_004 User exit for BAPI Verification of Outbound Deliveries
50. SHP_OBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
V50B0001 EXIT_SAPLV50I_003 User exit for BAPI Duplication of Outbound Deliveries
51. SHPCON
Delivery: Shipping confirmation
V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
52. SHPMNT
Shipping outbound
V55K0020 EXIT_SAPLV55K_020 IDoc SHPMNT: Modification Control/ Data before processing
V55K0021 EXIT_SAPLV55K_021 Processing of segments IDoc SHPMNT
V55K0022 EXIT_SAPLV55K_022 Update of user defined tables for inbound IDoc SHPMNT
53. SRCLST
Source List
MMAL0002 EXIT_SAPLMEAI_001 ALE source list distribution: inbound processing segments
MMAL0002 EXIT_SAPLMEAI_002 ALE source list distribution: inbound processing user defined data
54. SRVMAS
Master data service master
BASI0001 EXIT_SAPLBASI_001 Userexit IDoc inbound service master: segment
BASI0001 EXIT_SAPLBASI_002 Userexit IDoc inbound service master: database
55. TPSSHT
Shipping planning system: Transfer planned shipments
V56I0010 EXIT_SAPLV56I_010 IDoc TPSSHT01: Input of planned shipments: Modification of IDoc segments
V56I0010 EXIT_SAPLV56I_011 IDoc TPSSHT01: Input of planned shipments: modification of transport tab, processing
V56I0010 EXIT_SAPLV56I_012 IDoc TPSSHT01: Input of planned shipments: update of own tables
56. WHSCON
Delivery: Stock confirmation
V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
57. WMBBIN
Block Storage Bins
MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
MWMIDI04 EXIT_SAPLLIDI_004 Customer enhancement for IDoc WMBBID01
58. WMCATO
Reversal/Reversal request for transfer order
MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
MWMIDI03 EXIT_SAPLLIDI_003 Customer enhancement for IDoc WMCAI01
59. WMINVE
Inventory count input
MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
MWMIDO09 EXIT_SAPLLMDE_003 Customer enhancement for message WMINVE
MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
60. WMMBXY
IDoc Report goods movements in IM
MWMIDO08 EXIT_SAPLLMDE_002 Customer enhancement for message WMMBXY (goods movement) inbound
61. WMSUMO
Move storage unit
MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
MWMIDI06 EXIT_SAPLLIDI_006 Customer enhancement for IDoc WMSUID01
62. WMTOCO
Transfer order
MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
MWMIDI02 EXIT_SAPLLIDI_002 Customer enhancement for IDoc WMTCID01
63. WMTORD
Transfer order
MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
MWMIDO10 EXIT_SAPLLMDE_004 Customer enhancement for message WMTORD (Create TO) inbound
MWMIDO11 EXIT_SAPLLMDE_005 Customer enhancement for message WMTORD (Create TO) inbound
64. WMTREQ
Create/Cancel transfer order
MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
MWMIDI05 EXIT_SAPLLIDI_005 Customer enhancement for IDoc WMTRID01
65. WPUBON
POS interface: Upload sales documents (compressed)
WPUE0002 EXIT_SAPLWPUE_104 IDoc WPUBON01: prior to inbound processing
WPUE0002 EXIT_SAPLWPUE_105 Check, whether transaction of IDoc WPUBON01 is compressable
WPUE0002 EXIT_SAPLWPUE_106 IDoc WPUBON01: processing user segment
WPUE0002 EXIT_SAPLWPUE_109 IDoc WPUBON01: after to inbound processing
66. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
WPUE0002 EXIT_SAPLWPUE_130 IDoc WPUFIB01: prior to update
WPUE0002 EXIT_SAPLWPUE_131 IDoc WPUFIB01: processing user
67. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
WPUE0002 EXIT_SAPLWPUE_132 IDoc WPUFIB01: prior to inbound processing
WPUE0002 EXIT_SAPLWPUE_139 IDoc WPUFIB01: after to inbound processing
68. WPUKSR
POS upload cashier data
WPUE0002 EXIT_SAPLWPUE_120 IDoc WPUKSR01: prior to update
WPUE0002 EXIT_SAPLWPUE_122 IDoc WPUKSR01: processing user segment
WPUE0002 EXIT_SAPLWPUE_123 IDoc WPUKSR01: prior to inbound processing
WPUE0002 EXIT_SAPLWPUE_129 IDoc WPUKSR01: after to inbound processing
WPUE0002 EXIT_SAPLWPUE_152 IDoc WPUTAB01: prior to inbound processing
WPUE0002 EXIT_SAPLWPUE_159 IDoc WPUTAB01: after to inbound processing
69. WPUUMS
POS interface: Upload sales data (compressed)
WPUE0002 EXIT_SAPLWPUE_110 IDoc WPUUMS01: prior to update
WPUE0002 EXIT_SAPLWPUE_112 IDoc WPUUMS01: prior to inbound processing
WPUE0002 EXIT_SAPLWPUE_113 IDoc WPUUMS01: processing user segment
WPUE0002 EXIT_SAPLWPUE_119 IDoc WPUUMS01: after to inbound processing
70. WPUWBW
POS interface: Upload goods movements
WPUE0002 EXIT_SAPLWPUE_140 IDoc WPUWBW01: prior to update
WPUE0002 EXIT_SAPLWPUE_141 IDoc WPUWBW01: processing user segment
WPUE0002 EXIT_SAPLWPUE_142 IDoc WPUWBW01: prior to inbound processing
WPUE0002 EXIT_SAPLWPUE_149 IDoc WPUWBW01: after to inbound processing
71. WVINVE
Store physical inventory / sales price revaluation
WVFI0001 EXIT_SAPLWVFI_001 Inbound IDoc store phys. inv.: override Customizing
WVFI0002 EXIT_SAPLWVFI_002 Inbound IDoc store phys. inv.: process customer segment
IDoc Outbound User Exits
72. ACCONF
Confirmation of IDoc processing from the application
ACCID002 EXIT_SAPLACC2_040 IDOC ACCONF: Confirmation of processing in application
73. ACLPAY
Accounting: Inbound invoice
ACCID002 EXIT_SAPLACC2_030 IDoc ACLPAY: Userexit for header in accounting document (outbound)
ACCID002 EXIT_SAPLACC2_031 IDoc ACLPAY: Userexit for creditor line (outbound) in accounting document
ACCID002 EXIT_SAPLACC2_032 IDoc ACLPAY: Userexit for general line (outbound) in accounting document
ACCID002 EXIT_SAPLACC2_033 IDoc ACLPAY: Userexit for tax line (outbound) in accounting document
74. ACPJMM
Posting in accounting from materials management
ACCID002 EXIT_SAPLACC2_020 IDoc ACPJOU: Userexit Userexit for GL posting header in accounting document
ACCID002 EXIT_SAPLACC2_021 IDoc ACPJOU: Userexit Userexit for GL posting line in accounting document
75. ARTMAS
Create and change of material master (Retail)
MGV00003 EXIT_SAPLMV01_003 Enhancement for article master IDoc: Create
76. BLAORD
Purchasing contracts
MM06E001 EXIT_SAPLEINM_016 ALE distribution of contracts outbound enhancement for IDocs
MM06E001 EXIT_SAPLEINM_017 ALE distribution of contracts outbound enhancement for IDocs
77. BLAREL
Purchasing contracts
MM06E001 EXIT_SAPLEINM_003 Customer enhancements of data segment for outbound release documentation
78. COND_A
Conditions: master data for price determination
VKOE0001 EXIT_SAPLVKOE_001 Condition Transmission: Derivation of Filter Object E1KOMG
VKOE0001 EXIT_SAPLVKOE_002 Condition Transmission: Customer segments
79. CREMAS
Distribute vendor master
VSV00001 EXIT_SAPLKD01_001 Outbound: Create vendor segments
80. DEBMAS
Customer master
VSV00001 EXIT_SAPLVV01_001 Outbound: Create additional customer master segments
81. DELPKB
KANBAN call
MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
82. DIRDEB
Preauthorized withdrawal
FEDI0003 EXIT_SAPLIEDP_003 FI-EDI outgoing payments: Save PEXR segments (customer directory)
83. DOCMAS
Master document
CVDS0001 EXIT_SAPLCVALE_002 Userexit for ALEDVS (DOCMAS outbound)
CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
84. DOLMAS
Document-object links
CVDS0001 EXIT_SAPLCVALE_004 Userexit for ALEDVS (DOLMAS outbound)
CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
85. FIDCC1
Send entire FI documents (user exit 003/4)
F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
F050S002 EXIT_SAPLF050_003 FIDCC1 IDoc outbound: Change data / do not send
F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
86. FIDCC2
Send entire FI documents (user exit 005/6)
F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
F050S003 EXIT_SAPLF050_005 FIDCC2 IDoc outbound: Change data / do not send
F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
87. FIDCMT
Sending single items for FI-GL
F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
88. FIPAYM
Payment data
FIPAYM01 EXIT_SAPLF11A_001 USER-EXIT: message type FIPAYM, header data, outbound
FIPAYM01 EXIT_SAPLF11A_002 USER-EXIT: message type FIPAYM, reference data, outbound
FIPAYM01 EXIT_SAPLF11A_003 USER-EXIT: message type FIPAYM, bank data, outbound
FIPAYM01 EXIT_SAPLF11A_004 USER-EXIT: message type FIPAYM, GL data, outbound
FIPAYM01 EXIT_SAPLF11A_005 USER-EXIT: message type FIPAYM, partner data, outbound
89. FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
90. GSVERF
Cred. memo procedure
MRMN0001 EXIT_SAPLMRMN_001 Outbound IDoc for ERS/consignment settlement
91. HRMD_A
HR: Master data and organizational data (appl. system)
RHALE001 EXIT_SAPLRHA0_001 HR-CA: ALE outbound processing: Enhancement for receiver
RHALE001 EXIT_SAPLRHAL_001 HR-CA: ALE outbound processing: Change IDoc
RHALE001 EXIT_SAPLRHAL_003 HR-CA: ALE outbound processing: conversion info type / segment
92. INFREC
Purchasing info record
MMAL0003 EXIT_SAPLMEAO_002 ALE purchasing info record distribution: outbound processing
93. INVOIC
Invoice / Billing document
LVEDF001 EXIT_SAPLVEDF_001 User_Exit controll data IDoc_Output_Invoic
LVEDF001 EXIT_SAPLVEDF_002 User_Exit customer enhancement of segments outbound invoice
LVEDF001 EXIT_SAPLVEDF_003 User_Exit to avoid reading package data
LVEDF001 EXIT_SAPLVEDF_004 EDI Invoice: customer enhancement for reading additional data
94. KANBAN
KANBAN call
MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
95. LIKOND
Listing conditions
WSOR0001 EXIT_SAPLWSOE_001 Enhancement for assortments: outbound IDoc
96. MATMAS
Material Master
MGV00001 EXIT_SAPLMV01_002 Enhancement for material master IDoc: Create
97. ORDCHG
Purchase order/order change
MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
98. ORDERS
Purchase order / order
MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
99. ORDRSP
Purchase order / order confirmation
MM06E001 EXIT_SAPLEINM_009 MM EDI ORDRSP: customer enhancements tolerances (quantities/ date/price)
MM06E001 EXIT_SAPLEINM_014 MM EDI ORDRSP:enhancement price tolerances
MM06E001 EXIT_SAPLEINM_015 MM EDI ORDRSP: enhancement change of vendor material
SDEDI001 EXIT_SAPLVEDC_001 Customer enhancement for control record of order confirmation
SDEDI001 EXIT_SAPLVEDC_002 Customer enhancement for data records of order confirmation
SDEDI001 EXIT_SAPLVEDC_003 SD EDI ORDRSP: customer enhancement
SDEDI001 EXIT_SAPLVEDC_004 SD EDI ORDRSP:customer enhancement for reading additional data
SDEDI001 EXIT_SAPLVEDC_005 SD EDI ORDRSP: customer enhancement for configuration
SDEDI001 EXIT_SAPLVEDC_006 SD EDI ORDRSP: customer enhancement for configuration structures
SDEDI001 EXIT_SAPLVEDC_007 SD EDI ORDRSP: customer enhancement for header conditions
SDEDI001 EXIT_SAPLVEDC_008 SD EDI ORDRSP: customer enhancement for item conditions
WVFB0001 EXIT_SAPLWVFB_001 Customer exists for store order PO confirmation control seg.
WVFB0001 EXIT_SAPLWVFB_003 Customer exists for store order PO confirmation data seg.
100. PAYEXT
Extended payment order
FEDI0003 EXIT_SAPLIEDP_002 FI-EDI outgoing payments: Save PEXR segments (external payments)
FEDI0004 EXIT_SAPLIEDP_901 FI-EDI outgoing payments: New partner house bank
FEDI0004 EXIT_SAPLIEDP_902 FI-EDI outgoing payments: End of IDoc payment (VBLNR)
FEDI0004 EXIT_SAPLIEDP_903 FI-EDI outgoing payments: End of partner house bank
101. PICKSD
Picking data confirmation to customer delivery
VMDE0002 EXIT_SAPLVMDE_002 Shipping Interface: Message PICKSD (Picking, Outbound)
102. PRDCAT
Product Catalog
WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
103. PRDPOS
Product catalog item
WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
104. PRICAT
Price list / catalog
VPRE0001 EXIT_SAPLVPRE_001 PRICAT outbound processing (MAMT AUSP MAW1)
VPRE0001 EXIT_SAPLVPRE_002 PRICAT outbound processing (control record)
VPRE0001 EXIT_SAPLVPRE_003 PRICAT outbound processing (IDoc segments)
105. PROACT
Stock and sales data
WVMI0001 EXIT_SAPLWVMI_001 IDoc PROACT outbound: final action prior to sending
106. REMADV
Payment advice
FEDI0003 EXIT_SAPLIEDP_001 FI-EDI: Outgoing pmnt advice - Create extension of segments/ new segments
107. REQOTE
Inquiry
VEDE0001 EXIT_SAPLVEDE_001 Customer enhancement for control record of outbound quotation
VEDE0001 EXIT_SAPLVEDE_003 SD EDI REQOTE: customer enhancement
VEDE0001 EXIT_SAPLVEDE_002 Customer enhancement for data records of outbound quotation
VEDE0001 EXIT_SAPLVEDE_004 SD EDI REQOTE: customer enhancement for reading additional data
VEDE0001 EXIT_SAPLVEDE_005 SD EDI REQOTE: customer enhancement for configuration
VEDE0001 EXIT_SAPLVEDE_006 SD EDI REQOTE: customer enhancement for configuration structures
VEDE0001 EXIT_SAPLVEDE_007 SD EDI REQOTE: customer enhancement for header conditions
VEDE0001 EXIT_SAPLVEDE_008 SD EDI REQOTE: customer enhancement for item conditions
108. SRCLST
Source List
MMAL0001 EXIT_SAPLMEAO_001 ALE source list distribution: outbound processing
109. SRVMAS
Master data service master
BASO0001 EXIT_SAPLBASO_001 Enhancement: service master, check standard service catalog
BASO0001 EXIT_SAPLBASO_002 Userexit IDoc service master: receiver determination
110. SYPART
Partner profiles
SIDOC002 EXIT_SAPLEDI6_001 CA-EDI, Partner-IDoc: Exit after segment E1EDPP1
SIDOC002 EXIT_SAPLEDI6_002 CA-EDI, Partner-IDoc: Exit after segment E1ADRM0
SIDOC002 EXIT_SAPLEDI6_003 CA-EDI, Partner-IDoc: Final exit before sending
SIDOC002 EXIT_SAPLEDI6_004 CA-EDI, Partner-IDoc: Exit after segment E1ADRP0
SIDOC002 EXIT_SAPLEDI6_005 CA-EDI, Partner-IDoc: Exit after segment E1ADRE0
SIDOC002 EXIT_SAPLEDI6_007 CA-EDI, Partner-IDoc: Exit after segment E1EDP13
SIDOC002 EXIT_SAPLEDI6_008 CA-EDI, Partner-IDoc: Exit after segment E1EDP21
111. TPSDLS
Shipping planning system: Transfer delivery
V56I0001 EXIT_SAPLV56I_001 IDoc TPSDLS: Modification of delivery header group
V56I0002 EXIT_SAPLV56I_002 IDoc TPSDLS: Modification of delivery item group
V56I0003 EXIT_SAPLV56I_003 IDoc TPSDLS: Modification of package data group
V56I0004 EXIT_SAPLV56I_004 IDoc TPSDLS: Modification of entire IDoc
V56I0005 EXIT_SAPLV56I_005 IDoc TPSDLS: Modif. of delivery items relevant to shipment
V56I0006 EXIT_SAPLV56I_006 IDOC TPSDLS: User-defined determ. for location substitution
V56I0020 EXIT_SAPLV56I_020 IDoc control record modification in interface SD-TPS
112. WBBDLD
Assortment list: Material data
WBBE0001 EXIT_SAPLWBBI_001 Modification of replenishment list IDoc
113. WMCATO
Reversal/Reversal request for transfer order
MWMIDO02 EXIT_SAPLLIDO_002 Customer enhancement for IDoc WMCAID01
114. WMINVE
Inventory count input
MWMIDO04 EXIT_SAPLLIDO_004 Customer enhancement for IDoc WMIVID01
115. WMRREF
Release reference number
MWMIDO03 EXIT_SAPLLIDO_003 Customer enhancement for IDoc WMRRID01
116. WMTORD
Transfer order
MWMIDO01 EXIT_SAPLLIDO_001 Customer enhancement for IDoc WMTOID01
117. WP_EAN
POS interface: Upload / Download EAN assignments
WPDA0001 EXIT_SAPLWPDA_003 POS interface: Modification of IDoc data for EAN references
118. WP_PER
POS interface: Upload / Download person data
WPDA0001 EXIT_SAPLWPDA_008 POS interface: Modification of IDoc data for person related data
WPDA0001 EXIT_SAPLWPDA_013 POS interface: Add. Change pt. Analysis for WP_PER
119. WP_PLU
POS interface: Upload / Download material master
WPDA0001 EXIT_SAPLWPDA_002 POS interface: Modification of IDoc data for material master
WPDA0001 EXIT_SAPLWPDA_009 POS interface: Add. Change pt. Analysis for WP_PLU
120. WPDCUR
POS interface: Download exchange rates
WPDA0001 EXIT_SAPLWPDA_006 POS interface: Modification of IDoc data for exchange rates
121. WPDNAC
POS interface: Download products
WPDA0001 EXIT_SAPLWPDA_005 POS interface: Modification of IDoc data for follow-on items
WPDA0001 EXIT_SAPLWPDA_011 POS interface: Add. Change pt. Analysis for WPDNAC
122. WPDSET
POS interface: Download set assignments
WPDA0001 EXIT_SAPLWPDA_004 POS interface: modification of IDoc data for set assignments
123. WPDSET
POS interface: Download set assignments
WPDA0001 EXIT_SAPLWPDA_010 POS interface: Add. Change pt. Analysis for WPDSET
124. WPDTAX
POS interface: Download tax rates
WPDA0001 EXIT_SAPLWPDA_007 POS interface: modification of IDoc data for taxes
125. WPDWGR
POS interface: Download material group master
WPDA0001 EXIT_SAPLWPDA_001 POS interface: Modification of IDoc data for material groups
WPDA0001 EXIT_SAPLWPDA_012 POS interface: Add. Change pt. Analysis for WPDWGR
126. WPUBON
POS interface: Upload sales documents (compressed)
WPUE0002 EXIT_SAPLWPUE_102 IDoc WPUBON01: prior to update
127. WTADDI
Additionals
WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
128. WTADDI_CVB1
Additionals w/o 06
WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
General IDoc User Exits
ALE00001 EXIT_RBDPROSE_001 Old: exit for converting preproduction system to production
ALE00001 EXIT_SAPLBD11_001 User exit for the IDOC version changer
BDMO0001 EXIT_SAPLBDMO_001 Old: Enhancement to the ALE distribution reference model
KKCD0001 EXIT_SAPFKCIM_001 SAP-EIS: User exit for data compression of sender records (used for IDoc conversion)
KKCD0001 EXIT_SAPFKCIM_002 SAP-EIS: User exit for data summ. Of summarized records befo (used for IDoc conversion)
Link for the same:
http://erpgenie.com/abaptips/content/view/302/62/
Pls reward helpful points.
Regards,
Ameet -
IDoc Extension: Finding out user exit
Hi,
Is there any standard way of finding out user exit for the extended IDoc? like documentation...
Thanks and Regards,
MadhuHello
Here are some documentation link for defining idoc types
Customer Extensions, SAP and Customer Developments
Refer to this forum link.
Ale enhancement
Program names ZX... are reserved for includes of exit function groups
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/frameset.htm
Hope it will resolve your problem
All The Best
Priyanka
Do reward Points. -
User exit for idoc extension for material master (matmas05)
Hello all,
I have 10 custom fields added to anl idoc of basic type matmas05.
i created a new segment under parent segment E1MARA1
Now i want to find out the user exit where in i can write a code to read the data of this segment and populate into the data base table.
Can anybody provide me with the name of the user exit?
Regards,
RoshaniCheck enhancement MGV00001 in SMOD.
Exit Fm is EXIT_SAPLMV01_002
Regards,
Naimesh Patel -
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,
MattI myself fixed this problem. I made use of XLFA1-LIFNR to manipulate the partner numbers.
Thanks -
User exit for Internal Order SaveReplica or ALE/IDOC
Hi,
We're currently copying back internal orders from our PRD environment into QAS using the class method InternalOrder SaveReplica via the distribution model in BD64.
We've extended table AUFK to include some custom fields and are populating it nicely via the user exit provided. However, we want to include these values when we replicate the data back in our QAS environment.
The BAPI for method CREATE contains the "EXTENSIONIN" table so I think I know what to do there, but we are using SAVEREPLICA which doesn't offer any extra fields.
What is the best way to copy this data back into QAS?
Would it make sense to put a user exit RFC call in the QAS system to populate the values after reading them from the PRD system at the time of saving?
I can't find any user exits. We are doing this based off of change pointers.
Would you recommend using basic ALE, doing an extension to idoc type internalorders01 or something?
Thanks for any suggestions.Hi,
usage of specific combinations of internal orders + cost elements:
Create FI-validation rule (T-code OB28 or GGB1) using BSEG-HKONT, BSEG-AUFNR for call-up point 2. Assigne this rule to the comp. code(s) needed.
Best regards, Christian -
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,
Stephengo 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". -
Hi everybody!!!
Does anybody knows if exist any user-exit or badi for aleaud idoc???
We receive an Idoc from PI and we sent an Aleaud Idoc to Pi as Ack and we need populatel some fields.
Thanks a lottry an implementation of BADI IDOC_DATA_INSERT
we have successfully added an ALEAUD extension and populated fields within the extended segment the IDoc then gets sent to PI, however we have not managed to get PI to see those extended fields yet.
Colin -
User Exit for Inbound IDOC FIDCCP02 - FIDCC2
Hi All,
I am working on DOC type extensions, I extended basic IDOC type FIDCCP02 with one custom segment. This IDOC is associated with message type FIDCC2.
Custom segment have five fields, one out of five only i found it is BSEG table, rest of four is custom fields.
Now i want move these custom fields to custom table ( i.e ZEXT ), but not to BSEG table. i need a help for USER EXIT in inbound system to move the data from custom segment to custom table.
<u><b>Hierarchy of the segments structure with the custom segment which I added:</b></u>
E1FIKPF : FI Document Header (BKPF)
1) E1FISEG : FI Document Item (BSEG)
1.1 ) E1FISE2 : FI Document Item, Second Part of E1FISEG (BSEG)
1.1.1) Z1FISE2: Custom Segment for FI Posting IDOCS
1.2 ) E1FINBU : FI Subsidiary Ledger (FI-AP-AR) (BSEG)
2) E1FISEC: CPD Customer/Vendor (BSEC)
3) E1FISET: FI Tax Data (BSET)
4) E1FIXWT: Extended Withholding Tax (WITH_ITEM)Hi Sridhar,
I am suggesting you what ever i know. If u want to move the data from custom segment to custome table, then build a strucutre which refer your custom Segment, and manually you need to move those values from custom segment to custom table. for this first move data from that custom segments to work area after that insert that work are to custom table, hope this helps ypu.
Regrads,
Kumar. -
ORDERS05 IDoc User Exit - Create Sales Order
Greetings,
I'm working at a client where they are using the ORDERS05 IDoc in conjunction with the Process code ORDE to create customer finished goods sales orders in a 46C system. When the IDoc segment E1EDP19 is qualified with "003" and the article's UPC/EAN is supplied in the material field and conversion of the UPC to material is executed during processing when the sales order type is "ZEDI" however this conversion is not executed with any other sales order type, so I suspect a user exit routine however I checked the usual suspects.
MM06E001
VEDB0001
MCP20008
MM06E001
VEDA0001
But not code for the UPC to material conversion.
Any insight is alway appreciated and rewarded.
Thanks!Joseph,
Take a look in the function module EXIT_SAPLVEDA_001, see if there's an include there. We have an include there containing our Customisations, including for the E1EDP19 segment.
Cheers, Paul. -
Extended IDOC DEBMAS06 (MSG-Type DEBMAS) can't be filled using user EXIT
Hi,
I'm having a problem trying to fill an additional created segment (extension) for the IDOC DEBMAS06.
This IDOC is generatede from an ALE szenarion
and I need additional fields to fill using my extension.
With CMOD I created a new project using the enhancement VSV00001 (User exit Customer and vendor distribution Receipt/issue) to fill the additional field but, no way.
My extension segment will not appear onto this user exit.
I tried to search new exits, tried to make additional settind using ALE customizing but again now way, this onw extended segment will not come up in the user exit.
Please Help !
Many thanks
GaspareWhat do you mean by "My extension segment will not appear onto this user exit."? It will not be there, you will have to fill it and append it to the EDIDD table. In thh user exit, you will append the records for segment zzzzz(your extended segment) at the appropriate place.
Say the standard IDOC has the structure like below
A
--B
--C
D
and you added extended segment at the same level as B and C. In that case, you have to append the new segment records at the end.
If you added your segment as a child segment of B, then you will have to insert the records into the EDIDD table before the C segment.
Srinivas -
Hi,
For FBL5N, in individual change of line items, an user exit has been implemented. How do I extend that User Exit for Mass Change ?Joslyn-
The link between Basic IDOC type and IDOC extension is done in the partner profile first (WE20). After you have created an extension for your IDOC, you need to provide the same under Extension IDOC type in the outbound parameters of partner profile.
I am not sure about your requirement but from the user exit you are using, I guess you have more than one extension for customer master IDOC and you want to choose one based on certain parameters. The import and tables parameters of this exit should provide you enough information to do the same.
Let us know with specific questions if you need more info.
KK -
How to find the appropriate user exit for invoic02 idoc in idoc_output_invo
Hi all,
I am new to this community p
i have issue regarding the How to find the appropriate user exit for invoic02 idoc in idoc_output_invoic function module.........
thanks,Hi ,
welcome to SDN.
You can select the appropriate Customer exit accrding to the available parameters .
The list of exits available are
EXIT_SAPLVEDF_001
EXIT_SAPLVEDF_002
EXIT_SAPLVEDF_003
EXIT_SAPLVEDF_004
For Example , if you want to modify the Idoc data(EDIDD) you have to use the EXIT_SAPLVEDF_002. accodingly you can select the user exit according to the avaialable parametres.Use Table MODSAP fto get the Enhancement name.
Hope this Helps
Rgds
Sree
Edited by: Sree on Jul 23, 2010 12:11 PM
Maybe you are looking for
-
Upgrade from Panther to Tiger or Panther to Leopard
I'm operating a Powerbook 15" with a 1.33 G4 and 256MB RAM. I believe the specs for Leopard call for 512MB RAM. The question I have is, am I better off going with Leopard and upgrading the RAM or should I just go with Tiger and upgrade the OS? A litt
-
Hi there, I am expecting a bunch of Super 8 mm transfert that will be in the AVI format. What is the best way to import the AVI files into FCP in order to get the best quality and edit them ? Thanks in advance Ivan
-
I have more apps on my phone than my computer. When I SYNC my phone and computer, do I have to worry about losing the apps I have on my phone, or will the greater always add to the lesser? Will the apps I have downloaded to my computer that were over
-
i have a home theater system setup, goes from the spdif out on front of my A.2zs platinum card to the coax in on my receiver, and it worked great for about half an hour, then the music i was playing started to get a funny sound in intervals, like it
-
Cannot open ports on Sonicwall TZ 215
Use the wizard for a public facing server. It will create the address objects and ports you specify as well as the associated rules.