RFC_ERROR_SYSTEM_FAILURE during inbound processing
Hi,
I am getting below error while using startrfc for inbound processing.
RFC Call/Exception: SYSTEM_FAILURE
Group Error group 104
Key RFC_ERROR_SYSTEM_FAILURE
Message Port 'SAPCC4' does not exist in the table of port descriptions
I already have port SAPCC4 defined in my SAP system.
Please help.
Thanks & Regards,
HI ,
go to Idoc -number which is error generated..
see the control record..in EDIDC table..
see the Partner and go to we20 and see the partner and open inbound and see the message and open
details..
see whether the same port assigned to the Message type or ,,,if not assign..
if the port is TCP/IP or R/3 connection..go to t-code sm58 and see the error details for the RFC
destination assigned in the port..
Prabhudas
Similar Messages
-
AS2 adapter error during inbound processing
Hello,
We have upgraded PI to version 7.1 and now we are testing the Seeburger AS2 adapter.
We have received a testmessage from an AS2 partner and it is shown in the message monitoring of the Seeburger adapter workbench, with status succesfull.
Only the message is not on the integration server. The message is not shown in sxmb_moni or the message monitor of the RWB.
In the RWB the communication channel (CC_AS2_Sender) gives the following error:
"Message inititiation failed: Processing error"
The message itself gives the following error:
"Inbound message processing failed! performing rollback
Can anyone help us with this?
Thanks in advance.
Regards,
MarcoHi Marco,
the message is not forwarded to the intergration egine because there might be an error in your communication channel.
Are there any other modules in the module chain of this communication channel?
Can you check "default_trace" and "application_log" for exceptions (/j2ee/cluster/serverXX/log)?
Did you also restart the Java Stack after the Upgrade?
regards,
Daniel
Edited by: Daniel Rexter on Jun 30, 2010 2:59 PM -
CREMAS Update during inbound processing
Hi everybody,
I receive vendor information from a external system.
I want to import them by idoc type CREMAS05.
Everthing works fine.
But I have the problem that sometimes the external system sents a vendor number which is outside the allowed number range.
Therefore I want to implement a check. If this check is wron, I set a error status and message and the inbound will be canceld.
I have implemented Enhancement VSV00001 and User Exit EXIT_SAPLKD02_001 (Inbound: Read and process vendor segments)
the Problem is, that this user exit will be only called if the idoc includes a filled customer segment.
But in my case it didn't.
I had the idear to change the flag outside where are responsible for calling the user exit in that way, that evertime the exit will be called.
But there is no enhancement point there and I don't want to modify the SAP standard source.
How can I handle this?
Regards
ChristianIf you have duplicate Vendor number, it should not be able to reach to the point where it calls the subroutine call_transaction.
If you have implemented the implicit point at subroutine FILL_CRE_DATA_WITH_E1LFA1C, your code should be similar to this:
" do the validation of Vendor #
v_workflow_result = 99999. "<< this makes it to exit out and stops processing
CLEAR t_idoc_status.
t_idoc_status-docnum = f_idoc_control-docnum.
t_idoc_status-status = c_idoc_stat_input_error.
t_idoc_status-msgty = sy-msgty.
t_idoc_status-msgid = sy-msgid.
t_idoc_status-msgno = sy-msgno.
t_idoc_status-msgv1 = sy-msgv1.
t_idoc_status-msgv2 = sy-msgv2.
t_idoc_status-msgv3 = sy-msgv3.
t_idoc_status-msgv4 = sy-msgv4.
t_idoc_status-segnum = segnum.
t_idoc_status-segfld = 'LIFNR'. "<<
t_idoc_status-uname = sy-uname.
t_idoc_status-repid = sy-repid.
APPEND t_idoc_status.
t_return_variables-doc_number = f_idoc_control-docnum.
t_return_variables-wf_param = c_retv_error_idocs.
APPEND t_return_variables.
Regards,
Naimesh Patel -
IDoc Inbound Processing for CREMDM & DEBMDM
Hi experts,
I'd like to gather some feedback from you regarding the topic ERP IDoc Inbound Processing for CREMDM & DEBMDM. As you all know, there's currently no option to directly process CREMDM/DEBMDM IDocs in ERP. Currently you have to use PI for splitting the CREMDM/DEBMDM message into its related ADRMAS and CREMAS/DEBMAS IDocs.
My areas of interest are:
1) How satisfied are you with the current situation? Does the split work? Are there issues or problems in the current message handling? What are the Pro's and Con's from your point of view?
2) What would be the requirements for a CREMDM/DEBMDM handler? What would you expect? Maybe you have implemented something similar on project basis and could post some feedback?
One painpoint I'd see with a CREMDM/DEBMDM inbound is that you'll lose the IDoc Monitoring capabilities. The message split allows a single record tracing in the IDoc Monitor (as there is a 1:1 relation between IDocs and records). This changes for the mass processing. The monitor would display only the status of the IDoc and you'd need some other monitoring capabilities to check the results on record level. What are your thoughts about that? Is the monitoring important? Would the application log be a feasible solution for that challenge?
Additional comments are welcome, of course.
Best regards
Michael
PS: @ Matt, please contact me by mail. thanks.Hello ,
Here are some other pain areas regarding the message split :
1. Complicated monitoring proess & reprocessing error idocs : We have to monitor ADRMAS & CREMAS or ADRMAS & DEBMAS during inbound processing. Also we could not find any best practices to reprocess error idocs. E.g. If ADRMAS fails & CREMAS succeeds what is the impact . Also the impact if it is reveresed. We know for sure that if CREMAS fails , vendor will not be created / updated. But we could not find specific pointers for ADRMAS failures.
2. It is a tedious process to link CREMAS with corresponding ADRMAS idoc specially when SAP maintains internal number range for vendors.
3 . The process is complicated if you are managing customer or vendor contact information with contact address . We could succesfully implement the integration but it took us a while to reach end-point.
4. Splitting really does not seem to support if ERP maintains internal number range.
5. Another major issue we observed is , if ADRMAS is under process & corresponding DEBMAS or CREMAS is posted , it fails raising the message that Account is locked. Default serialization does work in ERP system . But overlap of few microseconds also cause this error.
Hope this helps !!
Please let me know if you need any other specific details since we have used MDM - ECC integration using PI to its maximum extent .
Regards
Yogesh -
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,
Swapnahi
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
<b>IDoc Inbound User Exits</b>
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
<b>IDoc Outbound User Exits</b>
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.. -
Combine MIGO and VL31N in inbound process
Hellow!
I want to use "Goods receipt blocked stock" to process low quality goods during inbound process.
We use "good receipt whith inbound delivery in WMS" scenario to recive goods from vendor.
I have not found a way to use "Goods receipt blocked stock" in delivery processing (vl31n). Only using MIGO.
Is it possible to use VL31N and post GR from delivery for good materials and MIGO to send low quality materil into "Goods receipt blocked stock" ?
Thanks for answers.
Andrey Garshin.Hi,
Miantenance of GR blocked stock with IM and WM is... Do MIGO with 103Mvt type . TO will get created automatically. Hence destination will be known. Putaway the stock and confirm the TO in WMS.
If you want to maintain GR blocked stock DIRECTLY in WMS....
Do GR with 103 Mvt type and post the stock to quality insoection. A fter QI release the stock from QI. Transfer the stock from Qualito to unrestricted.
If you want to maintain low valuated materila as GR blocked stock. Please create one storage type for GR blocked stock and post the stock to that particular storage type. I hope this will resolve your issue. Thanking you. -
Error : Pre Settings for IDoc inbound processing are missing error
Hi Experts,
There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
Thanks in advance.
Madhurima.I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
[iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299] -
NM7.1: Inbound processing was stopped because of server error (id=10)
Dear Experts,
We have migrated the 2.5 application to 7.1. Now when I am creating few transactions from mobile client say create or modify & trying to synchronize its giving me an error as stated below... I have copied the error code text from trace file of client.
Pls let me know if anyone has any clue so as what might be the reason behind it..!!
<r id="1268990872922" t="14:57:52" d="2010-03-19" s="D" c="000" u="" g="" m="HTTPSyncCommandIn#Error(errorId=10, messageText=Error during Uploading messages Id mismatch)">
<f n="SourceName" v=" [/CFS/Sync/Synchronizer/HttpSyncCommand]"/>
<f n="LocationName" v=" (com.sap.tc.mobile.cfs.sync.synchronizer.http.Command:execute)"/>
<f n="ThreadName" v="Thread-41"/>
</r>
<r id="1268990872923" t="14:57:52" d="2010-03-19" s="E" c="000" u="" g="" m="An error encountered on server: "Error during Uploading messages Id mismatch"; error code 10">
<f n="SourceName" v=" [/CFS/Sync]"/>
<f n="LocationName" v=" (com.sap.tc.mobile.cfs.sync.api.SyncManager:postMessage)"/>
<f n="ThreadName" v="Thread-41"/>
</r>
<r id="1268990872924" t="14:57:52" d="2010-03-19" s="E" c="000" u="" g="" m="Inbound processing was stopped because of server error (id=10): Error during Uploading messages Id mismatch ">
<f n="SourceName" v=" [/CFS/Sync/Synchronizer]"/>
<f n="LocationName" v=" (com.sap.tc.mobile.cfs.sync.synchronizer.http.HttpSynchronizer:readResponse)"/>
<f n="ThreadName" v="Thread-41"/>
</r>
<r id="1268990872937" t="14:57:52" d="2010-03-19" s="D" c="000" u="" g="" m="commit called on PersistenceSink with connection 27830759">
<f n="LocationName" v=" (com.sap.tc.mobile.cfs.pers.jdbc.core.JDBCPersistenceSink:commit)"/>
<f n="ThreadName" v="Thread-41"/>
</r>
Regards,
SaptakHi Amit,
Thanks for your inputs.. Do you have any idea behind this error, why does the client & doe messages go out of sync. And what can be done as a precautionary measure to avoid it..
Do you want me to try "Recover the device", or to reinitialise it ??
Because if I reinitialise the device then the user will not be able to sync again with same device & i will have to un-install & re-install the client & sync again...and this will create problems in production system.
I also tried to recover the device; it doesnt work this way.
Pls guide me...
Thanks in advance,
Regards,
Saptak -
Hi all
My scenario is soap to proxy scenario .while testing using soap to proxy i am getting " An error occurred during the processing of proxy E 00 001 The message can not be processed in plugin mode HTTP: in sxmb_moni sap pi .
Some times this interface is failing and some time its successfully processing.
While testing with successful xml data also i am getting the same error in sxmb_moni.
I modified the proxy inbound code where passing error message and still i am getting the same message.
Please suggestion the same for error solving.
Regards
Ravi.Hi,
I'm facing the same problem.
I wrote an very easy report. It works as intended, but when i set fillable='X' i get the error FPRUNX 001.
FP_GET_LAST_ADS_TRACE return following:
Begin operation:
Render, elapsed time = 16 ms.
# End operation: Render, elapsed time = 89 ms.
# Begin operation: UsageRights, elapsed time = 89 ms.
# End operation: UsageRights, elapsed time = 97 ms.#
...and the error string of FP_GET_LAST_ADS_ERRSTR is:
ADS: Request start time: Wed Jul 01 14:44:26 CEST 2009(200.101).
Any idea what the problem might be? -
DYNAMIC_CALL_FAILURE Error during proxy processing An exception with the ty
Hi,
SRM 7.0 contains 2 clients:
Sender: 100 for EBP, logical system is CLNT100
Receiver: 200 for SUS, logical system is CLNT200
both the clients are connected through PI 7.0, logical system of PI is CLNT001.
From SPROXY of 100EBP, i'm executing the outbound proxy, in moni sent msg success.
In PI also msg is processed.
But in SUS200, it is showing below error msg:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>CL_BBPX_TRADING_PARTNER_SUS_IN</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Pls help in resolving the same....
tnx n rgds,
baluHi,
How did you solve the issue? Can you please provide the solution.
Thanks,
-Devi Swain -
Hi Experts,
We have a web service hosted on PI and getting the Tax Jurisdiction values from Taxware via ECC(ECC has a TCP/IP connection to connect to Taxware system, From there ECC gets Taxjurisdiction Codes and gives back to PI).
When we make a call to this Web service following Error response has been given. Please let us know what could be the reason.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1 />
<SAP:P2>ZCL_GET_TAX_IN</SAP:P2>
<SAP:P3>GET_TAX_JURISDICTION_SYNC</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing Message E TAX_TXJCD 110 cannot be processed in plugin mode HTTP</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Thanks,
Sekhar.JHi,
We are using XI adapter. The same Web Service is working good in Development and Quality Enviroments, I am wondering why it is failing in Production Environement intermittently. And also in ECC we are using TCP/IP connection to fetch Tax Jurisdiction codes from TaxWare System. This TCP/IP connection was configured in SM59 of ECC. PI will make call to ECC and ECC will make call to TaxWare and returns the result back PI.
Thanks,
Sekhar.J -
Inspection lot problem during inbound delivery
Hi,
I am facing following issue during inbound delivery.
I have activated inspection type 01 in material master for a packing material. Created a PO for the material through ME21N. PO created. Now I am creating inbound delivery through VL31N with reference to PO no and vendor. When I am entering the storage location I am getting the below error..
Upon investigating the issue system is creating the inspection lot
But inspection lot is not showing in QA32/QA02.
checked various threads but not of much use. I am not able to proceed further.
Kindly help.
Thanks
KumarHi Kumar,
Plz check in PO history, if GRN is done. If yes then plz check in GRN quantity tab, if inspection lot is created. IN QA32, in dynamic selection enter the inspection lot and click on 'select all inspection lot' and check if it is created in system. If lot is prepared then as per the error message someone from your department must be processing it.
In Your inbound delivery screen check your tab status overview if it is A: GR not made or C: GR completed.
Also during inbound delivery storage location is picked up in inbound delivery automatically from PO you need not to enter it again.
Plz check else post screen shot of PO history and QA32.
Regards,
Priti. -
LSMW idoc Inbound Processing settings
Hi,
We have done LSMW with BAPI method to create Bank master.
In Idoc Inbound Processing settings -
We created partner type as 'B' i.e, for BANK
While creating Partner Number it is not allowing to create Partner Number. The error is "Enter a permissible partner number"
Please let me know what would be the problem.
Regards,
Hari
Edited by: Bhatlapenumarthy Hari Krishna on Sep 12, 2008 9:31 AMHi,
Use patner type as US only and LSMW as Patner number.
this will surely solve your problem .
plz do this way :
The first requirement is a file port for the file transfer. If required, create a port of the file type via Maintain ports. To do this, position the cursor on "File" and press Create. You should be in change mode. SAP recommends:
Port: LSMW
Name: Legacy System Migration Workbench
Version: 3 (IDoc record types SAP Release 4.x)
Outbound file Please enter a (dummy) physical directory and a file name, i.e. u2018filelsmwu2019 ·
As an addition, you can specify a tRFC port. This port is required, if you do not want to create a file during data conversion but submit the data in packages directly to function module IDoc_Inbound_Asynchronous.
SAP recommends:
Port: assigned by the system
Version: 3 (IDoc record types SAP Release 4.x)
RFC destination: Name of R/3 System
Name of port: Legacy System Migration Workbench.
Then the partner type should be defined or selected. SAP recommends:
Partner type: "US" (User)
As of release 4.5A, this partner type is available in the standard system. Up to release 4.0B inclusive, this partner type is not available in the standard program and should be added. SAP recommends:
Partner type: Create US
Report name: /SAPDMC/SAP_LSMW_PARTNERTYPES
Form routine: READ_USER
Short description: any.
Finally a partner number should be defined or selected. SAP recommends:
Partner number: LSMW
Partner type: US
Partner status: A (active)
Type: US
Language: DE or EN
Person in charge: Your user ID.
Activate IDoc inbound processing
reference : help.sap
thanx.
Edited by: Dhanashri Pawar on Sep 12, 2008 7:10 AM -
Wrong processing code used in inbound processing
Hi
We are on 4.6C and have configured a dist. model for material distribution using message type MATMAS. On receiving end IDOC is properly received but processed with code 51 which is "IDOC Interface not complete for message type".
While testing it in we19 with standard inbound option we found that its using process code AFSA though in the inbound partner profile its set to MATM. (In the table tbd52 AFSA is not even defiend for MATMAS but for ARTMAS) While using INBOUND FM option there with FM specified as IDOC_INPUT_MATMAS_MDM we were able to process the IDOC properly in receiving end. We are not sure which code is being defaulted to during automatic inbound processing but we guess its same as AFSA as shown during standard inbound option. It will be of great help if someone can explain what might have gone wrong.Dear Renjith
I got it. Actually the process code was correctly attached in sending system but in receiving system it was unfortunately set to AFSA which I ignored. Thanks a lot for the response.
regards
saurav -
CRM 2011+An error has occurred during report processing. (rsProcessingAborted)
Hi,
i have installed CRM 2011 on-premise version in Server A. Database and CRM 2011 Reporting Extenison in Server B. Both the server are 64 bit server and IIS 7.0 . i can able to browse the Report server url. USer as been added in Sql DB Logins and
as permission to Reportserver and ReportservertempDB.
i can able to access the CRM Reports only using Admin Credenttials that is from the credential which Report server is installed and configured
Error in server 1:
Web service request SetDataSourceCredentials to Report Server
(http://servername/Reportserver_XXXSQLSRVR)failed with SoapException. Error: An error has occurred during report processing. (rsProcessingAborted).
Error in Server 2: took this error From error log file
processing!ReportServer_0-1!7e4!03/16/2011-10:34:51:: e ERROR: Data source 'CRM': An error has occurred. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'CRM'. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException:
Caller S-1-5-21-1587242514-2812063576-513219026-1110 has insufficient privilege to run report as user 9f69b98c-c73d-e011-bd85-842b2b6567dd
processing!ReportServer_0-1!7e4!03/16/2011-10:34:51:: e ERROR: An exception has occurred in data source 'CRM'. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'CRM'. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException:
Caller S-1-5-21-1587242514-2812063576-513219026-1110 has insufficient privilege to run report as user 9f69b98c-c73d-e011-bd85-842b2b6567dd
processing!ReportServer_0-1!7e4!03/16/2011-10:34:51:: i INFO: DataPrefetch abort handler called for Report with ID=. Aborting data sources ...
processing!ReportServer_0-1!7e4!03/16/2011-10:34:51:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing., ;
Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'CRM'.
---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: Caller S-1-5-21-1587242514-2812063576-513219026-1110 has insufficient privilege to run report as user 9f69b98c-c73d-e011-bd85-842b2b6567dd
Eventvwr error in server 2:
Failed to unload app domain DefaultDomain. The following exception occurred: Error while unloading appdomain. (Exception from HRESULT: 0x80131015).
I tried the Following ways to fix it
1.added User as content manager
2.In CRM apppool i have Admin in identity column
its really paining when i'm unable to access the CRM 2011 Default Reports. got stucked for a day.
Thanks, Saraswathy KumaraveluHi All,
I encountered this same issue today after installing CRM 2011.
CRM 2011 on Server A
SQL and SSRS 2008 R2 on Server B
I found that I got the same errors described here when running the standard reports even after I had installed the Reporting Extension (CRM 2011 replacement for CRM 4.0 Data Connector). The reason I got the error was because the 'Data Source Type' had not
been updated in Report Manager.
Here's how I resolved:
1. Browse to Report Manager (http://SERVERB/Reports)
2. Open the Organisation_MSCRM folder
3. Click Show Details
4. Open the MSCRM_DataSource
5. Change the Data Source Type from Microsoft SQL Server
to Microsoft Dynamics CRM SQL
*Note: - This option is only available once Reporting Extension has been installed on SSRS Server.
6. Clear the contents of the Connection String box
7. Set the Connect Using: option to Credentials Supplied by user running the report
but do NOT check the
Use as Windows Credentials when connecting to the DataSource option.
8. Click Apply
9. Restart the SQL Reporting Services Service in
Reporting Services Configuration Manager
10. Test by running one of the Standard CRM Reports (e.g. User Summary)
Ta Da!! - Success!!
Hope this helps!
Maybe you are looking for
-
Help required integration opensso with OAM
Help required integration openssowith OAM Edited by: user13111258 on Mar 24, 2011 5:58 AM
-
Data getting deleted when doing the validation
Hi all, I have a web dynpro application to park an accounting document and I want the following functionality to it. When a user enters fund starting with 'P' then the cost center field should be greyed out and if WBS element field is not entered the
-
Hi All, In one of my SAP server having maximum dialog run time (rdisp/max_wprun_time) is 1300 Secs and the same value is applicable for every users who all are running in dialog mode. Can we increase this value only one or two users( let say this two
-
Which is the better choice when upgrading... CS4 or CS5? Advice needed. Thanks in advance...
-
How do I print a label that was create in labelview
We use LabelView to create and print product ID labels. What I want to do is print a product ID label after the product has pass the test. Like I said the label is all ready created all I need t do is print qty 1 or more.