EDI incoming doc verification
I am new to EDI processing. How do I verify docs company said they sent were received into SAP ? Company sending files is using startrfc to execute function module EDI_DATA_INCOMING. They execute EDI_DATA_INCOMING for each file sent. If they say they sent 10 files, how do I verify ?
Hi Denise,
What do you exactly want to do?
Do you want a automated note when a IDoc is processed. Or only on error. Or a report. Or a report on 3rd partys file numbers etc.
You may find WE06 may help you, use the trigger of status, eg: 53 - application document posted.
Similar Messages
-
Tax Jurisdiction code for EDI Incoming invoice
Hi,
We have implemented EDI incoming invoice using INVOIC02. The process code is INVL.The invoice is to be posted against a Purchase Order line item. It is noticed that the EDI invoice is not getting the Tax Jurisdiction code from the Purchase Order line . Instead the Tax Juridiction code is copied from the company code. However when we post the invoice manually using MIRO , then the Tax Juridiction code is copied from the Purchase Order. We understand that the system should take the Tax Jurisdiction code from the Purchase Order even for EDI invoices. Is it compulsory that we have to use the user exit EXIT_SAPLMRMH_014 in order to populate the Tax Jurisdiction code field TXJCD from the Purchase Order line? or is there any config required to enable the transfer of Tax Juridication code from the Purchase Order? In transaction OBCE there is a config to transfer the tax jurisdiction code supplied by the external vendor. If we do not check that box , then system is supposed to get the tax jurisdiction code from the Purchase Order.
Thanks
SukumarThe issue is resolved through OSS Note 506343. In the standard R/3 system, the tax jurisdiction code can't be written to invoice via EDI and only the Ship To Plant's Tax Jurisdiction Code is written to the invoice.
Regards
Sukumar -
EDI incoming invoice error M8 755 Enter a tax code in item...
All,
Can anyone tell me where I should look to resolve this issue? I'm trying to post an EDI incoming invoice for a PO. The PO has an tax code on the line item being invoiced.
Thanks
SandraLet me get into a little more detail. We have EDI incoming invoices working properly in our production environment. It is unlikely our mapping or our customization is incorrect. It is possible that something has been changed with customization but I have already looked there and did not see anything of concern.
I'm doing testing in our test environment using WE19, and I'm getting this error message although the idoc I create is similar to examples in production and the PO is also similar to what is in production.
I was hoping that someone had experienced a similar issue and would be able to point me in a direction that I have not already looked.
Regards,
Sandra -
EDI - Incoming Invoice Error and GR based Invoice Verification - 51 No GR
Hi,
We are implementing EDI for incoming invoices and use Goods Receipts based Invoice Verification. When processing an inbound IDOC Invoice (type INVOIC01) where the Goods Receipt has not yet been posted, then Inbound IDOC is siiting at Error Status, 51 - No GR documents found.
Is there any way we can process this as a Parked Invoice or for Verification in the background (MIRA)? because the current situation is a problem, as 95% of our Inbound Invoices will be received electronically before the Goods are Received.
The actual Vendor's delivery note is stored in the segment E1EDP02 (Qualifier 016), field BELNR.
Currently the IDOC as to sit in error until the Vendor's Delivery Note is Goods Receipted which can be several days later - SAP OSS Note 393883 fro 2001 suggests doing this, but surely this is a common situation. The IDOC sitting in error in WE02 in the list of IDOCs is difficult to isolate from true errors.
If this is was mnaul Invoice it could be processed through MIRA for background Invoice Verification later with program RMBABG00.
We havd SAP version ECC 6.0
I have spotted OSS Note 501524 which implies that is possible automatically Park Incoming EDI IDOC Invoices, has anyone tried this? and what would be the transaction/program that could be used to post several at once when the GR has been processed (similar to RMBABG00)Hi ,
You can use the program RBDMANI2 which will reprocess all the IDOCs (EDIinvoices )that have failed . You can schedule this program in the background and it will post all failed invoices which have the GR posted later .
We had the same scenario and we have scheduled this program as a daily job at night .
Regards,
Hari. -
we will be using EDI invoice processing for LIV.
invoice Type INVOIC01
Process Code INVL
Message Variant MM
we will receive inbound invoices from 150 Vendors through EDI.
I understand that in order to process IDOCs, i have to configure LIV
with EDI.
My question: in order to configure the parameters for EDI LIV i need to
create partner Profile. in our case i guess we have to create 150
partner profiles, one for each vendor, which means Vendor master must be created first.
In DEV golden client ( no data should exist), in order for
me to configure the parameters for EDI i have to create EDI Vendor master
( 150), and partner profiles for those Vendor master (150) and 150 for
each of the config step in (OBCA, OBCE, OBCD) then generate a transport
request.
The client wants a confirmation in order to allow us to create
data in the Golden Client? The other alternative is to open QA and PRD
for manual Config to configure these steps.
Any thoughts please?
Thank youHi,
I NEVER like having config open in the "live" client, but there are definitely situations where this is actually the only sensible option (however risky).
To have to create a whole range of master data in one client JUST so that you can transport config to another client does sound like it is crazy.
So if this is tightly controlled my personal opinion would be that it is OK to do this config directly into your live client (at an appropriate time, i.e. late at night, weekends etc.)
Steve B -
EDI - Incoming Invoices from Vendor
Hi,
This is Satya.
My question is
'When a vendor sends a credit memo via EDI will Oracle need to see that as a positive or negative amount?'
I will be thankful of all ur replies.
Thanks,
Satya.Hi ,
Partner profiles can be created directly in the quality cleint directly without opening the cleint.
As far as OBCA,OBCE,OBCD concerend,create a maintanance view and attach it to the transaction.Maintain those entries directly in Quality client without opening it.For example,create a maintance view for table T076B with the name Z_t076B.
Attach it to the transaction and move it to quality client and maintain the entries directly.
It works!.its a poven one -
Non PO Charges through EDI Incoming Invoice
Hi
I would be very thankful if somebody can answers these questions. I am designing EDI based invoice LIV.
1) Is it possible to post some charges in invoice which are without PO reference.Is it possible to post these kind of charges with EDI message INVOIC01 or we have to post through FI posting.? or we need to use INVOIC02
2) If possible through EDI in which segment of IDOC we will enter these charges with amt I am not able to find out the segment I tried in EIEDP01 but failed
3)Also is it possible to post credit memo also with EDI?
Thanks
[email protected]try out with segment E1EDP05.
-
EDI - Material doc not created
Hello,
Iam working with WMMBXY/WMMBID02 (WMMB) to post a GR on receipt of an inbound IDOC.Iam able to post the GR but material document is not created.Iam posting against an inbound delivery created against a stock transfer order.In my case I need a material document to be created.Can any one help me out in this?
Thanks,
LarryHi,
I believe you are posting it using the FM L_IDOC_INPUT_WMMBXY thru we19(i sa ur earlier post)...
Could you pls check the following...
goto se37...display the FM...put a break point at line no - 414-427 (the FM MB_CREATE_GOODS_MOVEMENT is called here)....
goto we19...execute on foreground and check the return values after this function call...like sy-subrc...the i_emkpf to get the material doc no. etc...
hope this helps...
Thanks,
Renjith -
Hi All ,
We are trying to post a Non PO invoice through IDOCS using Idoc Basic Type INVOIC01 but getting an error " Fill in mandatory field GL_ACCOUNT (table parameter GLACCOUNTDATA , row 000002 ) ''.
Any suggestions as to why this error could be occuring.
Thank You
Regards
SachinI think line item 2's GL account is typically populated from the PO's account assignment, but because this is not a PO related invoice that is why you are getting that error. For our NON-PO related invoices, we use the IDOC ACC_INVOICE_RECEIPT03. There is a segment E1BPACGL03 where we populate what GL account needs to be expensed. It is in that same segment that we also pass the other cost objects (business area/fund center) to charge. I quickly looked through IIDOC INVOIC01 and didn't find which segment it has that has the field GLACCOUNT listed. Hope that helps.
-
Interface program to transmit billing docs as edi 810
Hi experts,
I am new to ale/edi/idocs. I need to develop an interface program to transmit billing documents in a text file for sending them as edi 810 docs. Can anyone give me some idea on how to deal with this?
Thanks a lot...
Regards,
Abhinav
Message was edited by:
Neothanks karthikeyan...but i need help in the part after message control configuration in the edi outbound process...
-
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 -
Hi
EDI incoming vendor Invoices are getting blocked if vendor charging frights.
what we need to change to recieve with fright charge without block ?Hi biji123 ,
You should check out your customizing for EDI processing under the following path in SPRO:
Materials Management
->Logistics Invoice Verification
->EDI
->Enter Program Parameters
1. set parameter "processing" as ' '(SPACE).
2. maintain the setting for tolerance key 'PP','DQ' and 'DW' in
IMG/MM/LIV/Invoice Block/Set Tolerance Limits.
Then in the EDI-process system'll
1. at first take over the invoice item's amount and quantity from IDOC.
2. then make tolerance check with T-key 'PP', 'DQ' or 'DW' whether
difference between the invoice item's amount/quantity and proposed
amount/quantity is within the tolerance limit:
2.1.if the amount/quantity difference is within the tolerance limit,
the invoice can be posted directly via EDI-process,
2.2 if the amount/quantity difference is without the limit, but the
following messages have been set as 'warning':
. M8 082, M8 083, M8 084 and M8 085
(for amount check and normal PO/item),
. M8 081, M8 504, M8 087 and M8 088
(for quantity check and normal PO/item),
the invoice can be posted directly via EDI-process, but blocked for
payment and with Blocking reasons:
price(SPGRP = 'X') or quantity(SPGRM = 'X')
in the invoice item.
2.3 otherwise (if the amount/quantity difference is without the limit,
but aboved messages set as 'error'),
the invoice can't be created via EDI-process,
and the IDOC would have new status(51:error) and these messages would
be saved in it's application log.
Hope this helps.
Best regards,
Adam. -
Sender email address verification
During my recent DNS server outage (caused by XO DSL suddenly turning on filtering of port 53), I noticed something quite interesting with .Mac server and I am wondering if there is a way for Tiger server users to EASILY implement the same feature to reduce the inflow of spam?
When my DNS stopped, my .Mac account STOPPED accepting email from my work account, essentially saying there was no such account on my work server.
I obviously do understand that the fact that my DNS was not working and my server could not be verified was the reason for this, but it got me thinking....
Is there any easy way to put this sort of incoming email verification process on my OWN Tiger server (work)? i.e. Only accept delivery of incoming email AFTER you verify that the sender email address DOES correspond to a valid email account on the senders host?? - which means no bogus email address or hostnames accepted...
I think this would help cut down on a lot of Spam as these guys often send junkmail via bogus accounts/host names that cannot be replied to.
Any useful information regarding setting this up would be most appreciated
Thanks in advance - RohinMy question is ... wouldn't it make sense to check whether sender emails are valid before accepting email server connections.
There's not really any way of doing that, besides, that's not really what you want.
What you want is to ensure that the email comes from the person that it says it comes from. What you'd get is that the email says it comes from a valid email address. This is not the same thing.
Even now, 99% of spam emails are sent from valid email addresses - it's trivial to put any email address in the 'from' header.
Knowing that the From address is valid doesn't actually do anything to say that the person in the From header is the one who actually sent the message in the first place.
There are several industry-wide attempts and performing validation at the domain level, which is about as good as it's going to get in the near term. For more information check out Sender Policy Framework which defines (via DNS) which IP addresses are permitted to send email for a particular domain, and DomainKeys which uses digital signatures to validate the email.
Since both models require input from the domain owners, they won't be 100% reliable until all domains opt-in to the schemes. For now it can help validate that an email is from a legitimate domain, but the absence of a SPF or DomainKey doesn't necessarily mean the message is spam.
The only way to verify that the email comes from a valid user is some kind of confirmation - an email comes into your mail system which doesn't recognize the sender, so it holds the mail and sends a message back to the sender saying 'who are you?" and "if this message is legitimate, follow this link to unblock the message". The message is forwarded only after the sender confirms their identity and that the message is legitimate.
This has all kinds of issues, though including latency (it takes longer for messages to get to you), delays (what if the sender sends the message right before they leave on a week's vacation?), and not least the complete lack of support for any kind of automated messages, list, etc. that are sent from non-humans. -
How to make invoice verification process non-release process?
Hi friends,
I am doing incoming invoice verification (MIRO), once post it, I will have a message saying (document XXXXXX was created (document is blocked)). then I have to go to T-code MRBR to release it.
My question is: where could configure this process to be an non-release process?
Thanks,
LindaConfig. path.
MM \ LIV \ Invoice block \ Set tolerance limits
See also Item amount check (same path) in case this has been activated too.
Though presumably you want to have some tolerances unless it's a sandbox system.
Cheers,
Nick -
Payment Advice EDI - Reason Codes
HI All,
At the time of configure the Payment Advise through EDI, Is it Reason Codes configuration is Mandatory.
Ex :
Case 1 :
SAP - Customer Invoice : @ 1000
Customer Account Dr - 1000
To Sales Revenue - 1000
Incoming Payment Received file from EDI Transfer : @ 1000
Bank Main Account Dr - 1000
Customer Account or - 1000
Case 2
SAP - Customer Invoice : @ 1000
Customer Account Dr - 1000
To Sales Revenue - 1000
Incoming Payment Received file from EDI Transfer : @ 900
Will it accounting entry generate or will it stop due to the Partial Incoming Amount.
In this case Reason Codes will work. So Where can we insert the reason codes to capture the differential amount between the Invoice & EDI Incoming receipt
Regards
RajHi Satya
I think you are expecting payment advice to your company from bank.
For this you need create partner profile as BANK TYPE .
ANSI X12 txn is 820 - Payment Order/Remittance Advice
Please tell me is it ALE or EDI ?.
If it is EDI we are reciving the file from EDI Subsystem
It it is ALE means we are reciving the file from SAP R/3 only(genral practice).we can use ALE communication between SAP to NON-SAP systems also but when we are connecting to other company people will prefer EDI.
thanks
Maybe you are looking for
-
Is there any transaction that will change net price in a purchase order
Hi All, Is there any program / transaction where i can change the net price for few materials in the purchase orders (say 100 purchase orders) which has been created few days back. Please let me know at the earliest. Regards, PSS
-
Erron while using DynamicConfiguration in UDF
Hi All, I have create an UDF ,which imports com.sap.aii.mapping.api.*; package adn performs the following: /* UDF */ DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC
-
How to delete a files from MNT using scripting in OSD
Hi , I am looking a method for deleting a set of files present in virtual drive(MNT). Please let me know scripting methods that can achieve above things and i can add that in OSD FIle. Kindly advise Umeed4u
-
MacBook Pro (13-inch, Mid 2010) problems 10.8.3
Hi, I have problems wtih a macbook pro 13-inch mid 2010. Before the update of 10.8.3 I already had some problems, sometimes(a fewtimes in a week) the sytem stops and restarts. But after the update the system logs out every 5 minutes whem I play youtu
-
Can someone teach me via Skype?
I want to edit a one off 3 minute multicam film and I just need some guidance to get started. I'm a total beginner. I've currently got a trial version so I must do this soonish.