Partner group for inbound deilvery (DTAVI)

Hi experts,
Could someone tell me if inbound delivery (Document type DTAVI) has partner group? I have several partner functions in ERP on the inbound delivery that need to be mapped into GTS but I wanted to know if the partner functions also need to be added in the partner group for DTAVI.
Thanks,
Satish

Hi Satish,
As always, I have to somehow guess which version you are using. Recently, you would go to:
General Settings
> Document Structure
>> Define Document Types for Application Areas
Choose Dialog Structure "Inbound Customs Delivery", and assign the Partner Group to Document Type 'DTAVI'.
Regards,
Dave

Similar Messages

Partner profile for INBOUND IDOC

Dear experts,
Need your help to define partner profile for inbound idoc to R/3 system. There is a third party (Non SAP) based application from which idocs need to be sent to the R/3 system. There is no need to send an outbound idoc from the R/3 system. Can some one please suggest what are the steps to be taken to b configure the partner profile in the R/3 system for the inbound idoc?
Thanks,
Priyanka

Hi
This is not the right location to post this question.
You got to post this query in Data transfers section of SDN ABAP Development forums
Now regarding your question,
You need to create a Logical System with the help of the transaction SALE.
Assign the created LS to the client with the help of same transaction
Go to WE20 and create the partner with the same Logical System name
Now..as you are recieving the Inbound Idoc from external Non-SAP System, you need to maintain the message type in the Inbound Parameters by clicking on ADD Icon over there.
Before doing the above step, you got to create the connection between SAP and Non-SAP System.
Use transaction SM59 to do this. Type of connection would be R/3 I guess
Thanks
Hope it helps.

Partner Function for STO and relevant inbound delivery

Dear Expert,
i did the partner configuration for Vendor and STO with partner VN-vendor DP-delivery plant.
When i create the STO vendor UP07, both of VN and DP are UP07, but when i create the STO for UP07, no partner data come out for the PO, the partner data didn't copy out from vendor master.For standard PO not STO, the partner data are copied from vendor master automatically. Any advice any further more setting need to do?
I manually input the partner data for the STO, then i try to create inbound delivery, following incompleteness came out"Vendor : Account Number of Vendor or Creditor Missing",user need to manually input the partner number for LF-vendor.But when i check the partner setting for inbound delivery, LF is copied out from VN.Any more setting need to do to make sure the partner number of LF is auto copied from PO data.
Look forward to your reply,
Thank you and regards

Hello,
PLease check the vendor data created as a plant. Go to Vendor master and in purchasing view select extras -> additional Purchasing data-> in the plant assignment enter the Plant number. This will pull in the vendor details into the inbound delivery.
Thanks!!

Why the partner usuage tab is suppresed in account group for SH,BP,and PY

Hi All,
why the partner usuage tab is suppresed in account group for ship to party, bill to party and payer.
Regards,
MAllesh.

Maybe some one did it to not allow end user to access different Partner functions to those Account Groups, in which case it is better to consult your boss to rechange it. If it is like that by default, then you can change it on your own if it is required.
You can make it to 'change mode' in T Code OBD2. Select your Account Group, click Details and select Sales Area Data and then Partner usage and then change 'Business partner assignment' as Op Entry.
Now you will get your partner usage tab in change mode.
bye
Venkat - Hyd
Edited by: yajee venkat on Aug 22, 2008 1:44 PM

User exit to change partner for inbound delivery creation

Hello,
I have a requirement to change the partner number for
the inbound delivery creation.
I only see the USEREXIT_MOVE_FIELD_TO_LIKP but I am not sure if this is
the right user exit for this requirement.
Is there the user exit for modifying partner in the inbound delivery?
Thanks in advance,

HI
There is a program with which you can find the available exits as per your requirement. You have to execute the same and give your transaction code. Hope this helps...
*& Report ZFINDUSEREXIT
report zfinduserexit.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
select single * from tadir where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = tstc-pgmna.
move : tadir-devclass to v_devclass.
if sy-subrc ne 0.
select single * from trdir where name = tstc-pgmna.
if trdir-subc eq 'F'.
select single * from tfdir where pname = tstc-pgmna.
select single * from enlfdir where funcname =
tfdir-funcname.
select single * from tadir where pgmid = 'R3TR'
and object = 'FUGR'
and obj_name eq enlfdir-area.
move : tadir-devclass to v_devclass.
endif.
endif.
select * from tadir into table jtab
where pgmid = 'R3TR'
and object = 'SMOD'
and devclass = v_devclass.
select single * from tstct where sprsl eq sy-langu and
tcode eq p_tcode.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
write:/(95) sy-uline.
format color col_heading intensified on.
write:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
write:/(95) sy-uline.
loop at jtab.
select single * from modsapt
where sprsl = sy-langu and
name = jtab-obj_name.
format color col_normal intensified off.
write:/1 sy-vline,
2 jtab-obj_name hotspot on,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
endloop.
write:/(95) sy-uline.
describe table jtab.
skip.
format color col_total intensified on.
write:/ 'No of Exits:' , sy-tfill.
else.
format color col_negative intensified on.
write:/(95) 'No User Exit exists'.
endif.
else.
format color col_negative intensified on.
write:/(95) 'Transaction Code Does Not Exist'.
endif.
at line-selection.
get cursor field field1.
check field1(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
Do reward if useful...
Regards
Dinesh

Account groups for Partner Roles in Vendor Master

1. Can we use same account group to create the vendor master for the different partner roles? for the partner roles like goods supplier, invoicing party, order party, etc do all these need to have different account groups , example one account group for goods supplier, one account group for invoicing party, etc , etc.
2. why we need the configuration for partner role in purchasing documents besides partner role settings for vendor account group. what is the logic behind to have partner role dependent settings for purchasing documents.
If we do not maintain for partner role settings for purchasing documents what effects it will cause?

> 1. We can have 1 account group represent all partner role or separate account group for each role.
1.If we use the same account group, the field selection control for fields will be applicable to partner roles also. If we have made vendor schema as mandatory in vendor master than we have to assign to partner vendor also. Example ordering address will not require company code data only purchase data, it will not require also pricing procedure as mandatory as no price determination will be required for ordering address.
I think we have to use combination of account group -same account group and different account group will defining vendors for partner function.
Do we require to assign vendor schema group to following vendors roles- goods suppliers, invoicing party and payee.
If we do not assign vendor schema group will these partner role determine price from the VN partner role. For example VN (vendor) has vendor schema group assigned, no vendor schema group assigned to invoicing party, then while doing MIRO the invoicing party will be defaulted. Do the price determined for VN role will be populated for invoicing party in MIRO?
> 2. we need partner role in purchasing doc because we can copy partner role from vendor master to purchasing document
It means we need to assign similar roles in schema for vendor account group and purchasing documents. If you see the schema in config for partner determination in IDES system, different roles exists in vendor schema and purchasing document schema.
This is creating confusion for me to understand.
Please clarify
2. we need partner role in purchasing doc because we can copy partner role from vendor master to purchasing document

User Exits for Inbound Process

hi all
can any one please give some example user exits in inbound process and explain the omportance of user exits
Thank you,
Swapna

hi
Userxits allow us to add our own functionality to SAP standard program
without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
Types of User exits
1. Menu Exits
2.Function exits
3.Table exits
4.Screen exits
5.Keyword exits
6.Field exits.
also refer to the links below.. can get more info on user exits
list of user exits
http://www.planetsap.com/userexit_main_page.htm
can also get the list of user exits thru..
Tcode: CMOD -> Utilities -> SAP Enhancements -> F8 Execute
User Exits Notes:
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/81/8c5738ee806b0ee10000009b38f889/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
below are some of the useful invound and outbound userexits
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)
===
User exits for Pricing.
1.USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ
2.USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
3.USEREXIT_FIELD_MODIFICATION
4.USEREXIT_FIELD_MODIFIC_KZWI
5.USEREXIT_FIELD_MODIFIC_KOPF
User exits for Sales order
1USEREXIT_DELETE_DOCUMENT
2USEREXIT_FIELD_MODIFICATION
3.USEREXIT_MOVE_FIELD_TO_VBAK
4.USEREXIT_NUMBER_RANGE
5.USEREXIT_SAVE_DOCUMENT
User exits for billing
1.USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
2.USEREXIT_ACCOUNT_PREP_KOMPCV
3USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
4USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB
5.USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
====
Reward if USeful
Thanx & regards
Naren..

Multiple Logical Systems in Partner Profile for one instance

Can we create multiple Logical Systems in Partner Profile (WE20) for one instance or one System? If it is possible, can we create Logical System with respect to Plant/Country?

I am not quite sure if I understood your problem completley. But let's see...
Usually you use on on MSCS Cluster Group per SAP instance. So you have your already existing NW 7.0 ABAP stack in a separated Cluster Group, and you create a new Cluster Group for your new Java system.
You can find more information about it in this guide here on SDN:
Link: [High Availability;
More information about High Availability Setups for SAP System can be found here on SDN:
Link: [High Availability]
If you want to use the same database for your clustered ABAP stack and your new Java stack you can do a MCOD installation.
Please see Link: [SAP Note 388866 - Multiple Components on One Database - Installation|https://service.sap.com/sap/support/notes/388866]
Hope this helps.
Best regards,
Mathias

Confirmation control key check for inbound delivery creation

Hi,
Currently, in the Client's company, the process of receiving goods from purchase orders looks like that (SAP-wise):
- create a purchase order,
- receive goods using MIGO and automatically create an inbound delivery,
- pack the delivery and post goods receipt.
Recently, some patches have been installed, including one described by note 1602047 (which basically enforces checking confirmation control keys if goods receipt assignment and goods receipt relevance are activated for inbound deliveries). Note says that it only affects two-step stock transfer and creation of automatic inbound deliveries using SPED output but it seems it also affects other basic processes like PO receipt in MIGO.
Now, when using the old control key (that had MRP-Relevant and GR-Relevant fields checked), the system is unable to automatically create an inbound delivery after the goods receipt is posted with MIGO (with message VL148 - Not possible to create an inbound delivery). I learned that this is because the "GR Assignment" field must be checked in the confirmation control key so it's possible to automatically create aninbound delivery after receiving a purchase order in MIGO.
After changing the confirmation control key to have the missing field checked it's not possible anymore to receive goods from PO in MIGO as the PO requires shipping notification in order to be processed in MIGO thus requiring of manual creation of an inbound delivery.
Is there any way to skip this check so the process would remain the same (this model has been working fine for few years in the Client's system) and the inbound delievery would be created automatically after posting the receipt in MIGO?
Thanks in advance,
Piotr

Hi,
don't know if you found a solution, but we received the following message from SAP:
The advent of the new version requires some attention to the users. It
was necessary to avoid inconsistencies which in the past version the
system was susceptible.
Main Program SAPMM07M
Source code of MM07MLVS
sy-msgid VL sy-msgty E sy-msgno 148
I have checked the process and through debugged I could confirm the
following information SAP is providing to all similar incidents reportedfor us:
Error message VL 148 is issued if in the confirmation control key used
in the purchase order, the fields for MRP-relevance (T163G-KZDIS),
GR relevance (T163G-WEREL) and GR assignment indicator (T163G-WEZUO)
are not set.
The correction of note 1602047 was necessary to avoid inconsistencies
(table EKES) in the purchase order. Without having the GR assignment
(T163G-WEZUO) set, there is no unique reference created between the
purchase order history (table EKBE) and the inbound delivery
confirmation (table EKES) at goods receipt which leads to a problem if
several inbound deliveries exist for the same purchase order.
If you set T163G-WEZUO to 'X', this assures that, for an inbound
delivery, the confirmation record (EKES) belonging to this inbound
delivery (EKES-VBELN) is also accurately updated at goods receipt.
How to solve the issue?
Use a confirmation control key with the GR assignment indicator set
and then create the inbound delivery with VL31N. If you want to be able
to create the inbound delivery with reference to a certain line item in
the PO, use transaction VL34.
If you still want to use transaction MIGO, there is the following
workaround:
- Create a purchase order without any confirmation control key
- Create a goods receipt (GR) in transaction MIGO with reference to this PO and post the GR to a non-HU-managed storage location
- Create a transfer posting with MIGO using movement type 311 to
transfer the goods from the non-HU-managed storage location to the
HU-managed storage location.
As the transfer posting is an additional step for the user, the whole
process could be automated using a partner storage location
(T001l-PARLG) for the GR which then triggers (through a modification)
the BAPI 'BAPI_GOODSMVT_CREATE' to create the transfer posting without
user interaction.
I hope to have satisfied you on the reason why it is now happening and
also I believe you can explain to business that it is a new behavior
necessary done from SAP side to avoid worse situations, we are aware of
potential dissatisfaction it might cause. SAP Support is always
available to clarify any issue.
Sorry for not having a more positive answer.
I hope it helps!
Leentje

Partner functions for a specific customer not seen in XD03 but appears in XD02

Hello SAP Gurus,
I have a situation where a partner functions for a specific customer not seen in XD03 but appears in XD02, In XD03 only one partner function (Ship to) appears but in XD02 (Sold to, Ship to, Bill to and payer appears), from the customer master I can see that account group for this customer has been changes to Sold to (Z001) from Ship to (Z002).
I checked in settings for OB20 transaction for display customer centrally, it is in Display mode as required and not suprresed would like your inputs as to why this is happening and what can be done to fix this.
Thanks and Regards
Mohammed Roshan

Hi ROshan,
Open customer master in XD02 sales view and save it then check in XD03 it should display the partner functions.
As you said the account group has been changed I think the records needs to be saved again.

Post Goods Receipt for Inbound Delivery using WHSCON IDoc

Dear All
Currently I am working on a big project dealing with EDI connections to our logistics partner for the Export business. The entire message flow between Lindt and our partner should be via EDI. Our SAP release is (still) 4.6c.
We will create two kinds of despatch advice messages, one for inbound deliveries and one for outbound deliveries for customers.
I would appreciate your support in the following problem that I am facing with the inbound delivery scenario:
We create stock transport orders (purchase orders, POs) for the goods intended to be delivered into the plant at our partner
We create a delivery (type NL = replenishment delivery) for this POs
As soon as we post the goods issue we send the despatch advice (as EANCOM D96A DESADV message) to our partner.
At this point the delivery is basically completed, i.e. packing status (PS) and goods movement status (GM / GS) are equal to 'C' (= completed).
Our logistics partner uses the same EDI message to send us the goods receipts data, e.g.:
We dispatched 50 units of a product => QTY:50:12
The partner received indeed 50 units => QVR:50:66
Please note that we do not use the QVR segment for the quantity difference (between despatched and received quantity) but it contains the received units. This way we avoid negative values in the QVR segment.
When the logistics partner sends back the DESADV message containing the received quantities (QVR segment) we want to make
the goods receipts for the products in the original stock transport order and
upate the message flow in the delivery
My idea was to transform the incoming DESADV message into a WHSCON.DELVRY03 IDoc based on the documentation in: [Delivery Interface|http://help.sap.com/saphelp_crm40/helpdata/en/e2/654b15a9f411d184ec0000e81ddea0/content.htm]
In the delivery header control E1EDL18 I used QUALF = 'PGI' (Post goods issue).
I prepared an inbound WHSCON IDoc according to the documentation mentioned below. I managed to get some feedback from the Idoc processing implying that the system tried to do the goods receipt in the PO but failed.
To make a long story short here are my questions:
Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
Does anybody have an example on how to fill the WHSCON IDoc?
Or is my approach a cul-de-sac ?
Kind Regards
Uwe
PS: A related question can be found here: Goods Receipt in PO AND Message Flow Update in Inb. Delivery using WMMBXY

Hi Uwe,
Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
The binary answer would be no. You should use WMMBXY or MBGMCR instead.
But if we are doing goods receipt against Inbound delivery then answer is YES with additionally E1EDL18-QUALF = 'PIC' populated. But please remember no partial receipt is possible against Inbound Delivery.
We should populate E1EDL20-VBELN with our Inbound delivery number and line item info should go to E1EDL24.
I have done a similar interface recently where we are doing receipt against Inbound delivery. But our case was a bit complex because we had to support against Inbound delivery. So we had to go for a custom solution on top of IDOC_INPUT_DELVRY.
Hope this helps. Let me know if you have more questions.
Regards,
Rudra

Idoc WHSORD for inbound delivery

Hello,
We want to send inbound deliveries to an external WMS (not SAP WM) by using an output in the inbound delivery.
I tried to use idoc WHSORD (basic type DELVRY01) as for Outbound delivery.
I obtained an error message when processing the output : "The message record of the message control contains a partner role with a partner type LS that cannot be used here. Only the 'KU' and 'LI' partner types are allowed."
Configuration done (same as outbound delivery) :
Output : Medium "6 EDI" / Partner type LS
Partner profile (WE20) : Partner type LS / Partner role LS /Message control : Application E1 / process code DELV.
Finally, I've been able to generate one idoc from the inbound delivery by using medium "A ALE" and partner type LI "vendor". But I need to do it for a LS partner as we do want to maintain partner profile for each vendor.
Is this due to some missing configuration linked to application E1 (i.e allow partner type LS ?) ?
How can we solve this ?
Thanks a lot for your help

Hi zhiqiang,
In order to test inbound idocs, you can use transaction WE19 to create manually idocs.
As pre-requisite, you have to maintain ALE configuration : port and partner profiles.
Then in WE19, you can create an idoc from message type : fill all the fields you need to and delete unuse segments. Then click on "Standard inbound" and your idoc will be received in your SAP system.
Check the status in transaction BD87.
To fill correctlly your idoc :
1. You can find documentation on message type in transaction WE60 (when you go in this transaction, check the documention is "active" => Goto => user settings => "Documentation output" and "field value output" must be ticked)
2. In WE19, for some fields, if you press F4, you will get list of possible values.
Good luck,
JP

Partner Profile for IDOC - configuration

Hi..
I have an inbound IDOC TPSSHT01, which has been extended by adding a Z segment.. But I keep getting an error message.. The IDOC is created with status 56 and the message says "No inbound profile found".. I have configured the Inbound profile to include the message type 'SHIP' in WE20 and also added the message type in WE57 and WE82... Do i need to do any further settings?
Thanks
Rishi

hI,
Please use transaction code WE20 to generate inbound partner profile
Goto WE20 transaction of the client 200 where you are posting the idoc and maintain the partner profile for the inbound type for the idoc type and the corresponding message type of SHIP. This is because you would have maintained it as the outbound parameter from client 100. But at the receiver end also you need to configure the same.
Status 56 comes up when the partner profile for the idoc type is not maintained. Once its maintained, the idocs which you post will go into 53 if its successfully processed and to 51 if its failing due to any inbound processing program validation
*Reward points
Regards

Just one partner profile for SAP XI?!

Hi,
well i have some thoughts concerning configuring the partner profile on sender side.
I have different systems to which e.g. IDocs will be send to. Therefore i was thinking to set one partner profile for each connected system.
But on the other hand it is also possible to just configure one partner profile, e.g. called SAP XI, and seperate the different IDocs inside this partner profile because of different Message-Types of the Outb-parameters, and inside this because of the IDoc-Type.
So what is the most propriate way to solve this, is there a suggestion by SAP?!
thx in advance, Jens

Hey guys,
Just thought I'd add my experiences here.
In one of our implementations we created partner profiles with respect to XI. We had multiple source systems , but the Target ECC team was like, we do not care who sends the data to XI, as far as we are concerned we get data from XI. So we create only one partner profile. We agreed to this and so all Idoc's posting from XI had the XI as the sender partner name. The project went into production and things were fine.
Then comes the next release. And what do we realise, that the same Idoc will not be posted from XI but for different source systems with different formats. The Inbound processing for the idoc was also being changed stating that Idoc from Source system A needs to be processed with this T code and Idoc's from System B with this code. reason was different bsuiness rules across different geographies.
Now, at this juncture we realised in vain that it would have been better had we maintained the partner profiles with respect to the End Systems . having it with respect to XI caused issues in the fact that we are unableto trace out which Idoc belonged to which system.
Since, then we always recommend all partner profiles with respect to End Systems and not with respect to XI. Helps the business also understand how many idoc's were posted for which source system and so on.
Just my 2 cents and experience here. Would love to heard more on this topic as well.
Regards
Bhavesh

How to change some partner data for defined partner role?

Hello SDN!
I need to set another ID and address for partner both in header and positions. Data comes from CRM ISA. I'm using extended BADIs with methods IF_EX_CRM_ISA_BASKET_HEADCHANGEHEAD_BEFORE_ORDER and IF_EX_CRM_ISA_BASKET_ITEMSCHANGEITEMS_BEFORE_ORDER for header and positions. These methods have tables CT_PARTNER and CT_INPUT_FIELDS. CT_PARTNER already has record needed for me (with role '000000002' and given REF_GUID). I need to change PARTNER_NO field with our ID for this record. But if I do this, focuses in ShipTos comboboxes in order.jsp become reseted after any refresh/actualisation of page. Record in CT_INPUT_FIELDS also created and filled properly.
How I can properly change PARTNER_NO field?
Regards, Lev

Hi Lev,
Local variables maybe?
Have a look at the CRM_PARTNER_OB function group for reading. storing and deleting the partner data.
Regards,
Patrick.

Partner group for inbound deilvery (DTAVI)

Similar Messages

Maybe you are looking for