Inbound Processing With BDC

Hi!
   Can any one tell me why there is a need to go for BDC in Inbound IDOC Processing.
   We can directly take the data from Fun Module & update the database why there is need for BDC.
Thanks
   Rahul

hi,
One of the feature in BDC is to view the error in foreground manner ,so you can trace the error path easily and can easily rectify it,
also BDC have the capability to re-run your session at any time i.e, even if the destination is not available you can re exhibit the process once again.
So in these cases we can go for BDC rather than any FM.
REward Useful Points
Regards,
Siva

Similar Messages

Inbound Processing with reference to user defined Message type

Respected Readers,
I have created a segment with fields
Matnr
mbrsh
mtart
vpsta
maktx
meins
matkl(Total 7 fields)
I have created a idoc also and a message type and assign the idoc with message type.
Now i have set the communication partners also and created the distribution model with my message type and distributed also to the reciver side.
Now as it is not the standard message type like MATMAS so we cannot use the tcode BD10 to send the material.Instead of it i have to write the program to create the idoc for sending it.
So i have created the program for the generation of IDOC.
Upto here picture is clear.
In the case of Inbound in standard we use the tcode BD11 to get material but same thing as we are not using the Standard Message type we have to create our program.
Now in this case i have written a function module and that function module is attached to the process code and process code is attached to the message type and message type is attached to the partner profile.
i have done the assignments in we57 and bd51 also.
Now idoc is created in the inbound side with status 70.
but i am not getting how to upload this data in standard tables Mara and Makt.
So that if i go to tcode MM02 and give the respective Matnr ,it should display that material.
First tell me what i have done is the right procedure or i have to make somechanges somewhere .
Secondly if you please give me the function module code for inbound processing to upload the data in this standard table( mara ,makt) so that material is created in the reciver side also.i will be very thankful to you.
I am only using seven fields in creating the material.
Please kindly send your answers and not links .
Thanks

i have done the same thing and used same parameter in import ,export ,tables and exception tab.
i have written some code also .
But i am not getting the code to upload the data in the standard tables so that material should be get created automatically as soon as the data get uploaded
in tables.
Somewhere i have read that you have to use the BDC concept Call transaction method to upload the data.
But how to use the BDC code in Function module , i am not getting.
Please can you send any example of code for this task.

Inbound process with mov. type 101 in decentralized WM environment

Hi Gurus,
I am new to the decentrilezed WM environment and i would appreciate if someone could help me.
My process has the following characteristics:
1. Creation, in the ERP system, of the inbound delivery with reference to the PO. The delevery will be distributed.
2. The inbound delivery is generated with item category widn, that is not relevant for putaway on the dWM
3. In VL06I / VL32N post goods receipt. The stock should stay on 902 storage type.
The problem is that, when the delivery is not relevant for putaway, the system cannot find the storage type to post the goods and the tables of the reference movement types are correctly configured. In a not distributed scenário, this should be an easy process...
ERROR: T331 entry for warehouse number 800 and storage type not found.
If i check the relevancy for putaway this error never happens.
Help please. Thank you in advance.
Best regards.

Hi,
If the item category is marked as relevant for putaway, the process of distributing it to the decentralized system automatically sets the item to not relevant for putaway, since putaway takes place in the decentralized system.
So please check the settings in your ERP as well as Decentralized system once again.
Thanks,

Inbound process with WM and HU

Hi Friends ,
I am exploring different possibility Standard SAP supports for goods receipt process through Inbound deliveries.TO make things simple right now I am only finding possibilities for EXTERNAL Material receipt only.
The steps I know invloved in Inbound delivery process are (with WM and HU)
1) PR - Source assignment - PO - Release PO
2) Advance shipment notification (ASN)
3) Inbound delivery creation
4) Packing of material on Goods receipt
5.1) Put-away - Automatic TR creation
5.2 ) Put-away - Automatic TO creation
5.2 ) Put-away material - TO Confirmation
6) PGR
Now I am looking for different configurations by which can automate processes mentioned above from point 2 to 6.Like
2 and 3 ) ASN / Inbound delivery : I know that ASN can be received from vendor (in the form of idoc) and can create Inbound delivery automatically.But what if Vendor doesn't provide ASN message , how can we create deliveries for expected material ? Do we need to use VL06I ??
4) Once the Inbound delivery is created , I know we can automate packing process ... not sure about the configuration.I only know that this invloved condition technique where we create Conditions / schema / condition records ... BUT where do we assign that SCHEMA ( like pricing schema is attached to PORG group / Vendor grp )
5.1 ) Do we always need to have a TR to get TO created against Goods receipt OR can we can ask system to create TO directly without any TR ?
5.2 ) TO Creation - Automatic TO creation as soon as the packing is completed.
Where is this setting ? I understand there are two process 1) real time TO creation 2) Background TO Creation. For immediate TO creation I can see a configuration in IM-WM movement type assignment configuration , is that all ??
5.3 ) TO Confirmation -.Like TO Creation , do SAP also provide functionality to CONFIRM TO immediately or through Background Jobs ?? What are the required settings ?
6) How can we automate the PGR process ?
Sorry for this long query , but I hope there are many other friends who are interested in knowing all such possibilities.
Thanks in advance for all your help.
Regards
Shrey

2 and 3 ) ASN / Inbound delivery : I know that ASN can be received from vendor (in the form of idoc) and can create Inbound delivery automatically.But what if Vendor doesn't provide ASN message , how can we create deliveries for expected material ? Do we need to use VL06I ??
    Option 1: You can use transaction VL34 to create inbound deliveries by PO, Plant and the delivery date.
    Option 2: You can use transaction VL31N and click the Purchase Orders to create inbound deliveries.
4) Once the Inbound delivery is created , I know we can automate packing process ... not sure about the configuration.I only know that this invloved condition technique where we create Conditions / schema / condition records ... BUT where do we assign that SCHEMA ( like pricing schema is attached to PORG group / Vendor grp )
    First we have to create the packing instruction in POP1.
--> Give a packing instruction name.
--> Then in the line 1 - Enter P and the packaging material
--> Then in the line 2 - Enter M and enter the material to pack and give the quantity to pack in the packaging material. Eg: In each pallet how much quantity to be packed.
Second go to the transaction POF1.
--> Enter RCPT and based on the combination Material/Plant/Vendor, select it and enter the Material and the Packaging Instruction you created before.
--> Then you can do the autopack in VL32N.
5.1 ) Do we always need to have a TR to get TO created against Goods receipt OR can we can ask system to create TO directly without any TR ?
--> We can create the TO directly from the VL32N.
*5.2 ) TO Creation - Automatic TO creation as soon as the packing is completed.
Where is this setting ? I understand there are two process 1) real time TO creation 2) Background TO Creation. For immediate TO creation I can see a configuration in IM-WM movement type assignment configuration , is that all ??*
   SPRO - Logistics Execution - Warehouse Management - Activities - Transfers - Set Up Autom. TO Creation for TRs / Posting Change Notices
5.3 ) TO Confirmation -.Like TO Creation , do SAP also provide functionality to CONFIRM TO immediately or through Background Jobs ?? What are the required settings ?
   SPRO - Logistics Execution - Warehouse Management - Activities - Transfers - Define Movement Types
   Then select the Warehouse and the movement type 101 and select the option "TO item can be confirmed immediately"
   This will confirm the TO as and when the TO is created.

File to idocs - sequence of inbound processing

Hi everybody,
we have a file to (2) idocs scenario. In XI we map the received data of vendors into two idocs (adrmas and cremas). After building the idocs we send them in that sequence to the reveiver systems (recommended). The problem is that in the receiver system very often the idoc cremas wants to be processed before adrmas is ready. This leads to the error "vendor xy is blocked by user sapale". Especially for massprocessing I get a lot of these error-messages in bd87. As workaround I processed all the error-idocs by the report rbdmani2. (First step adrmas - second step cremas) But then I face missing data in some cases in table lfa1 - which seems to me that the sequence of 1. adrmas and 2. cremas was not correct processed.
Is there a possibility for inbound processing with the rule process adrmas - wait until ready - process the associated cremas and so on?
I checked the sap-help article for seralisation - but we could not achieve a better result by queing the outgoing messages in the xi.
Thanks very much.
With kind regards
Jörg

You have to get a solution based on the following concepts
1. Do not use BPM it is not efficient
2. Understand what is the difference between an IDOC in received state and processed state. Received state mean IDOC is saved into IDOC table. Processed state mean IDOC processed into the business system.
3. You can ASK BASIS guy to turn on the immediate IDOC processing option in SAP system,so that SAP process the IDOC as soon as it arrive in IDOC table. This is not efficient, in case if your SAP system has to process SAP online client request and SAP document (inbound and outbound) same time.
4. Understand the concept of standard based integration, mean integration system provide the option to business parties to provide the successfull message transfer.
Based on all these points I recomend you to follow the steps below.
1. Extract each record from the input files into two idocs.
2. Send the first IDOC to the receiving system
3. Send the second IDOC to a ESB storage such as DATABASE, JMS Queue, MQ Series Q (if you have available) or even to another File.
4. Develop an RFC module to check the status of the IDOC being send to the receiving system. Status here mean whether the IDOC data processed into the business system. You can do this lookup using a custom RFC lookup using the attribute connecting the first IDOC record with second IDOC.
5. Process the records (second IDOC) from the intermediate storage using the RFC lookup into the business system updates its status as ready to deliver.
6. Using another process such as FILE to IDOC or JMS to IDOC or JDBC to IDOC send each record which are ready to process from intermediate storage to the receiving system.
7. Create a report using FILE or JMS, JDBC adaptor module to keep track of these three stage processing, so that in case an inconsistency happed you will have an auditing trace available.
This is the standard based integration approach.
ABAP guys, BASIS guys they may not get it when then repair a BMW in local auto workshop, cuz I had to fight with them 4 years ago to make it happen in Verizon supply chain project where I had to accomplish the same concept in SAME IDOCS you mentioned here.
BPM, turning on immediate processing of IDOCS etc will end up in buying another 16 CPU hardware and BASIS guys or ABAP guys running BAD record IDOC processing report for 350.00 hr consulting FEES.
SAP is a good company and XI is a good product, as long as it is being used as per right usage.

Inbound process codes

Hi
I'm trying to post inbound idocs to ztables. For this I have created a custom FM z_idoc_input_delvry and assigned it a custom process code. I would like to know what are the values for the ALE table fields in WE42 like Application-object type, start event,etc.
Thanks,
A.P.

Hi A.P,
The IDoc tab section is used to setup methods and events for error processing of IDocs of a specific message type.
For example, message type INVCON will use object type IDOCINVCON.
Please check this link for more information on inbound processing with object methods including error handling.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Hope this will help.
Regards,
Ferry Lianto

Monitoring inbound processing and Sync/ Async communication on PI7.11

Hi All,
I am new to PI. We have following two requirements to be done on PI 7.11
1)     Monitoring inbound processing (Txn Code SWF_INB_MON)
2)     Monitoring Sync/ Async communication (Txn Code SXMS_SAMON)
Kindly let me know how should I proceed or what document should I follow or any scenario is to be configured.

Hi,
    1. Start inbound processing monitoring with transaction SWF_INB_MON or SWF_INB_ADM.
           Note that you require administrator authorization for transaction SWF_INB_ADM
    2. You can monitor the throughput of the inbound processing either on the basis of individual process system or system-wide. In this way you can display the throughput figures in any discrete time range, right down to seconds. A similar display for message packages allows you to monitor inbound processing with the same detail."
     3. You can display runtime information about individual messages, for example, the total runtime of a message in inbound processing or just the runtime of a specific section of the inbound processing. For monitoring individual messages click on "Display Message Packages".
regards,
ganesh.

IDoc to Soap, with BPM - Permanent error in BPE inbound processing

Hi Experts,
IDoc to Soap, with BPM - > Permanent error in BPE inbound processing
How to rectify this any issue???
Thanks-
sk

Hi,
The inbound processing encountered a permanent error and the queue therefore stopped.
The error message "Permanent error in BPE inbound processing" may be caused by the following:
- At the start or when you process a process instance, the inbound processing encounters an exception that was not handled. This exception is triggered, for example, by a transformation step, a synchronous send step or a control step but it was not caught in an exception handler branch. If the exception that was not handled occurs in the first transaction of the started process instance, the system does not write the process instance to the database but it sets the queue that has this error message to the error status.
Refer to the help in Note 1082099
- The inbound processing triggers this error if the correlation evaluation shows that a message should be delivered to a process instance that has the status "error". Since delivery to process instances that contain errors is not permitted, the queue is stopped.
Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message and use transaction SXMB_MONI_BPE "Continue Process Following Error" (or transaction SWF_XI_SWPR) to continue. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.
Check whether your system contains other process instances that have errors in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process Following Error" or transaction SWF_XI_SWPR.
Use the report RSWF_CRL_MAINTAIN to check all of the correlation instances in question or the relevant process instances that you can reach using "Display Work Item".
- Messages that cannot be delivered because no correlation instance can be found may lead to the error that is mentioned here. Check whether the causes that are outlined in Note 1094028 affect your case.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful.

Inbound interface with multiple IDOC processing

Hi,
I have to create an inbound interface which has to be triggered only when a batch job is completed in the middleware. The batch job will create 2000 records and 1 IDOC for each record. I have to get all the 2000 IDOCs and then process them together. I have to manipulate the data in these 2000 IDOCs and update them in a SAP table.
Please let me know how do I proceed with this.
Should I go with a custom func module or a custom program?
Thanks,
Abhishek

Hi,
Custom function module with standard parameters : For details refer to the topic Implementing Inbound Processing on page 85 of the
[ALE Programming Guide|http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf]
regards,
Advait

Strange problem with backgroung processing of BDC for Transcation CLMM

Folks,
I have encountered strange problem with BDC.I created an ALV report from output i select any number of rows and hit insert class button on top. If i select less than 10 row and use this statement
call transaction 'CLMM' mode 'N'
,it works fine but if i select more than 10 rows ,the sy-subrc after this statement
call transaction 'CLMM' mode 'N'
is 1001 means an error. I cant understand this problem of Mode N. if i put statement
call transaction 'CLMM'
(foreground processing) here ,everything works fine. Do you have any idea?
Nirad

Hi,
The problem is due to the screen size which can differ between foreground and background mode.
A screen with 10 table rowsin foreground does not necessarily mean same number of rows would be available in background mode.
Hence its always better to create recording with Simulate Background Mode as checked.
When you enter transaction code 'CLMM' in SHDB transaction and start recording, check Simulate Background Mode.
Hope this helps!
Cheers,
Vikram

B1358 error while posting inbound idoc with a FM

Hi
We are trying to post and inbound IDOC with the help of an rfc and eventually creating an invoice from a bdc wrapped in the RFC
The idocs are successfully pushed to R/3 while they are not getting posted and the error code in we02 is as follows
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.
Note: we are using a custom function module
regards
krishna

Hi Krishna,
I assume that your function module processing the IDOC does not follow the ALE/IDOC processing rules.
Please check out the programming guidelines in the SAP Online Help under:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm</a>
Important are the parameters and tables that need to be returned, containing the correct IDOC processing status. Please take the IDOC processing quite serious in regards to complete Logical Unit of Works.
Best regards,
SIlvia

ALE IDOC Inbound processing using IDOC_INPUT_ORDERS

Hi experts,
I am stuck up with IDOC inbound processing.
Can you please let me know about the process in Receiving Purchase Order from the customer system and creating Sales Order in the SAP system? using FM IDOC_INPUT_ORDERS. I have an Idea about WE20, NACE etc.
Can you please explain me about the process on how to go about it?
Kind regards,
Shiva.

Hi,
I have moved this thread from [ABAP, General Forum |ABAP Development; to [Data Transfers Forum|ABAP Connectivity;.
The forum Data Transfer is the place to discuss LSMW, ALE, BDC, Data Transfer Techniques, Batch Data Communication, Legacy System Migration Workbench, Application Link Enabling, IDOCs, BAPIs.
Please, the next time check the most appropriated forum category before posting. Thus you have more chance to have your question answered !
Best Regards.
Marcelo Ramos

User Exits for Inbound Process

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

hi
Userxits allow us to add our own functionality to SAP standard program
without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
Types of User exits
1. Menu Exits
2.Function exits
3.Table exits
4.Screen exits
5.Keyword exits
6.Field exits.
also refer to the links below.. can get more info on user exits
list of user exits
http://www.planetsap.com/userexit_main_page.htm
can also get the list of user exits thru..
Tcode: CMOD -> Utilities -> SAP Enhancements -> F8 Execute
User Exits Notes:
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/81/8c5738ee806b0ee10000009b38f889/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
below are some of the useful invound and outbound userexits
IDoc Inbound User Exits
1. ACC_BILLING
Accounting: Post invoice (OAG: LOAD RECEIVABLE)
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
2. ACC_EMPLOYEE_EXP
FI/CO: HR posting GL (AcctngEmplyeeExenses)
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
3. ACC_EMPLOYEE_PAY
FI/CO: HR posting AP (AcctngEmplyeePaybles)
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
4. ACC_EMPLOYEE_REC
FI/CO: HR posting AR (AcctngEmplyeeRcvbles)
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
5. ACC_GL_POSTING
Accounting: General G/L account posting
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
6. ACC_GOODS_MOVEMENT
Accounting: Post goods movement (OAG: POST JOURNAL)
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
7. ACC_INVOICE_RECEIPT
Accounting: Post invoice receipt (OAG: LOAD PAYABLE)
 ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
8. ACLPAY Accounting: Inbound invoice
 ACCID001 EXIT_SAPLACC1_031 IDoc ACLPAY: Userexit for creditor in accounting document
 ACCID001 EXIT_SAPLACC1_032 IDoc ACLPAY: Userexit for GL posting in accounting document
 ACCID001 EXIT_SAPLACC1_033 IDoc ACLPAY: Userexit for taxes in accounting document
9. ACLREC
Accounting: Billing document
 ACCID001 EXIT_SAPLACC1_011 IDoc ACLREC: Userexit for debitor in accounting document
 ACCID001 EXIT_SAPLACC1_012 IDoc ACLREC: Userexit for GL posting in accounting document
 ACCID001 EXIT_SAPLACC1_013 IDoc ACLREC: Userexit for taxes
10. ACPJMM
Posting in accounting from materials management
 ACCID001 EXIT_SAPLACC1_021 IDoc ACPJOU: Userexit for GL posting in accounting document
11. ARTMAS
Create and change of material master (Retail)
 MGV00003 EXIT_SAPL1001_003 Enhancement for article master: IDoc inbound
12. BLAOCH
Purchasing contract change
 MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
 MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
 MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
13. BLAORD
Purchasing contracts
 MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
 MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
 MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
14. BLAREL
Release order documentation for distributed contracts
 MM06E001 EXIT_SAPLEINM_004 Customer enhancements for release documentation inbound
15. COND_A
Conditions: master data for price determination
 VKOI0001 EXIT_SAPLVKOI_001 Interchange of Conditions: Inbound Processing Modifications E1KOMG Segment
 VKOI0001 EXIT_SAPLVKOI_002 Interchange of Conditions: Inbound Processing Customer Segments
16. CREMAS
Distribute vendor master
 VSV00001 EXIT_SAPLKD02_001 Inbound: Read and process vendor segments
17. DEBMAS
Customer master
 VSV00001 EXIT_SAPLVV02_001 Inbound: Read and update additional customer master segments
18. DELINS
Delivery schedule/JIT schedule
 VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
 VED40001 EXIT_SAPLVED4_002 Copying Data to Screens for Incoming EDI Docs
 VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
 VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
19. DESADV
Delivery: Shipping notification
 LMELA010 EXIT_SAPLEINM_010 Customer enhancement shipping notification inbound: line item
 MM06E001 EXIT_SAPLEINM_006 Customer enhancements for shipping notification inbound
 V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
 V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
 V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
 V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
 V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
 V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
20. DOCMAS
Master document
 CVDS0001 EXIT_SAPLCVALE_001 Userexit for ALEDVS (DOCMAS inbound)
21. DOLMAS
Document-object links
 CVDS0001 EXIT_SAPLCVALE_003 Userexit for ALEDVS (DOLMAS inbound)
22. EDLNOT
EDL delivery notes
 VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
 VED40001 EXIT_SAPLVED4_002 Copying Data to screens for Incoming EDI Docs
 VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
 VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
23. FIDCC1
Send entire FI documents (user exit 003/4)
 F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
 F050S002 EXIT_SAPLF050_004 FIDCC1 IDoc inbound: Change IDoc / do not process
 F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
 F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
24. FIDCC2
Send entire FI documents (user exit 005/6)
 F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
 F050S003 EXIT_SAPLF050_006 FIDCC2 IDoc inbound: Change IDoc / do not process
 F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
 F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
25. FIDCMT
Sending single items for FI-GL
 F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
 F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
26. FINSTA
Bank Statement
 FEDI0005 EXIT_SAPLIEDP_201 FI-EDI: inbound - bank statement/ Lockbox - Final processing
 FEDI0005 EXIT_SAPLIEDP_202 FI-EDI: inbound - bank statement/ Lockbox - Processing of segments
27. FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
 F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
28. GSVERF
Cred. memo procedure
 VED50001 EXIT_SAPLVED5_001 User Exit for Condition Value Tolerances in the Self- Billing Procedure
 VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
 VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
29. HRMD_A
HR: Master data and organizational data (appl. system)
 RHALE001 EXIT_SAPLRHA0_002 HR-CA: ALE inbound processing: Export parameter
 RHALE001 EXIT_SAPLRHAL_002 HR-CA: ALE inbound processing: Change info type data
 RHALE001 EXIT_SAPLRHAL_004 HR-CA: ALE inbound processing: conversion segment/ info type
30. INFREC
Purchasing info record
 MMAL0004 EXIT_SAPLMEAI_004 ALE source list distribution: inbound processing userdefined data
 MMAL0004 EXIT_SAPLMEAI_003 ALE purchasing info record distribution: inbound processing segments
31. INVOIC
Invoice / Billing document
 FEDI0001 EXIT_SAPLIEDI_001 FI-EDI: Invoice receipt - Determine G/L account per invoice line
 FEDI0001 EXIT_SAPLIEDI_002 FI-EDI: Invoice receipt - Determine add. acct assignm. per line item
 FEDI0001 EXIT_SAPLIEDI_003 FI-EDI: Invoice receipt - Fill the screen field 'Allocation'
 FEDI0001 EXIT_SAPLIEDI_004 FI-EDI: Invoice receipt - Determine the segment text
 FEDI0001 EXIT_SAPLIEDI_005 FI-EDI: Invoice receipt - Determine the name of the BDC session
 FEDI0001 EXIT_SAPLIEDI_011 MM-EDI: Invoice receipt - Determine purchase order item
 FEDI0001 EXIT_SAPLIEDI_101 FI-EDI: Invoice receipt INVOIC01 - additional assignment
 FEDI0001 EXIT_SAPLIEDI_102 FI-EDI: Invoice receipt INVOIC01 - add data
 FEDI0001 EXIT_SAPLIEDI_111 MM-EDI: Invoice receipt INVOIC01 - additional assignment
 FEDI0001 EXIT_SAPLIEDI_112 MM-EDI: Invoice receipt INVOIC01 - add data
 MRMH0002 EXIT_SAPLMRMH_011 Logistics Invoice Verification:inboud EDI message, company code
 MRMH0002 EXIT_SAPLMRMH_012 Logistics Invoice Verification:inboud EDI message, control flags
 MRMH0002 EXIT_SAPLMRMH_013 Logistics Invoice Verification:inboud EDI message, assignment
 MRMH0002 EXIT_SAPLMRMH_014 Logistics Invoice Verification:inboud EDI message, segments
 MRMH0002 EXIT_SAPLMRMH_015 Logistics Invoice Verification:inbound EDI message, before posting
32. LIKOND
Listing conditions
 WSOR0001 EXIT_SAPLWSOI_001 Enhancement for assortments: inbound IDoc
33. MATMAS
Material Master
 MGV00001 EXIT_SAPLMV02_002 Enhancement for material master IDoc: Update
34. MRESCR
Create reservation
 SAPLMEWB EXIT_SAPLMEWB_001 Customer exit for processing of reservations via BAPIs
35. ORDCHG
Purchase order/order change
 MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
 MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
 VEDB0001 EXIT_SAPLVEDB_001 SD EDI incoming change orders: read additional data from IDoc
 VEDB0001 EXIT_SAPLVEDB_002 SD EDI incoming change orders: additional data for dynpros
 VEDB0001 EXIT_SAPLVEDB_003 SD EDI incoming change orders: further activities after calling
 VEDB0001 EXIT_SAPLVEDB_004 SD EDI incoming change orders: closing activities per
 VEDB0001 EXIT_SAPLVEDB_005 SD EDI incoming change orders: closing activities by order block
 VEDB0001 EXIT_SAPLVEDB_006 SD EDI incoming change orders: setting order type
 VEDB0001 EXIT_SAPLVEDB_007 SD EDI incoming change orders: additional checks of IDoc
 VEDB0001 EXIT_SAPLVEDB_008 SD EDI incoming change orders: error handling
 VEDB0001 EXIT_SAPLVEDB_009 SD EDI incoming change orders: additional checks of IDoc segments
 VEDB0001 EXIT_SAPLVEDB_010 SD EDI incoming change orders: manipulation of status ecords
 VEDB0001 EXIT_SAPLVEDB_012 SD EDI incoming change orders: change internal table
36. ORDERS
Purchase order / order
 MCP20008 EXIT_SAPLMCP2_008 User exit: Processing of purchase order header
 MCP20008 EXIT_SAPLMCP2_009 User exit: Processing of purchase order item
37. ORDERS
Purchase order / order
 MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
 MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
 VEDA0001 EXIT_SAPLVEDA_001 SD EDI incoming orders: read additional data from IDoc
 VEDA0001 EXIT_SAPLVEDA_002 SD EDI incoming orders: additional data for dynpros
 VEDA0001 EXIT_SAPLVEDA_003 SD EDI incoming orders: further activities after calling
 VEDA0001 EXIT_SAPLVEDA_004 SD EDI incoming orders: closing activities per order
 VEDA0001 EXIT_SAPLVEDA_005 SD EDI incoming orders: closing activities by order block
 VEDA0001 EXIT_SAPLVEDA_006 SD EDI incoming orders: setting order type
 VEDA0001 EXIT_SAPLVEDA_007 SD EDI incoming orders: number of ordering party
 VEDA0001 EXIT_SAPLVEDA_008 SD EDI incoming orders: error handling
 VEDA0001 EXIT_SAPLVEDA_009 SD EDI incoming orders: additional checks of IDoc segments
 VEDA0001 EXIT_SAPLVEDA_010 SD EDI incoming orders: manipulation of status records
 VEDA0001 EXIT_SAPLVEDA_011 SD EDI incoming orders: change internal table
 WVFB0001 EXIT_SAPLWVFB_002 Customer exists for store order PO confirmationdata seg.
38. ORDRSP
Purchase order / order confirmation
 MM06E001 EXIT_SAPLEINM_005 Customer enhancements for order confirmation inbound
 MM06E001 EXIT_SAPLEINM_007 Customer enhancements inbound confirmation: reading
 MM06E001 EXIT_SAPLEINM_008 Customer enhancements inbound confirmation: final
 WVMI0001 EXIT_SAPLWVMI_003 ORDRSP VMI inbound, modification before creating purchase order
39. PORDCR
Create purchase order
 SAPLMEWP EXIT_SAPLMEWP_002 Customer exit for processing of purchase orders via BAPIs
40. PREQCR
Create purchase requisition
 SAPLMEWQ EXIT_SAPLMEWQ_001 Customer exit for processing of requisitions via BAPIs
41. PROACT
Stock and sales data
 WVMI0001 EXIT_SAPLWVMI_002 IDoc PROACT inbound: prior to processing
42. REMADV
Payment advice
 FEDI0002 EXIT_SAPLIEDP_101 FI-EDI: Incoming pmnt advice - Extended allocatn of IDOC -> applicatn data
 FEDI0002 EXIT_SAPLIEDP_102 FI-EDI: Incoming pmnt adivce - Closing allocatn of IDOC -> applicatn data
43. REQOTE
Inquiry
 VEDQ0001 EXIT_SAPLVEDQ_001 SD EDI inbound inquiry: read additional data from IDoc
 VEDQ0001 EXIT_SAPLVEDQ_002 SD EDI inbound inquiry: additional data for dynpros
 VEDQ0001 EXIT_SAPLVEDQ_003 SD EDI inbound inquiry: further activities after calling
 VEDQ0001 EXIT_SAPLVEDQ_004 SD EDI inbound inquiry: closing activities per inquiry
 VEDQ0001 EXIT_SAPLVEDQ_005 SD EDI inbound inquiry: closing activities by inquiry block
 VEDQ0001 EXIT_SAPLVEDQ_006 SD EDI inbound inquiry: setting inquiry type
 VEDQ0001 EXIT_SAPLVEDQ_007 SD EDI inbound inquiry: number of sold-to party
 VEDQ0001 EXIT_SAPLVEDQ_008 SD EDI inbound inquiry: error handling
 VEDQ0001 EXIT_SAPLVEDQ_009 SD EDI inbound inquiry: additional checks of IDoc segments
 VEDQ0001 EXIT_SAPLVEDQ_010 SD EDI inbound inquiry: manipulation of status records
 VEDQ0001 EXIT_SAPLVEDQ_011 SD EDI inbound inquiry: change internal table
44. SBINV
Credit memo procedure with invoice creation
 VED50001 EXIT_SAPLVED5_002 User Exit for messages in the Self-Billing Procedure SBINV
 VED50001 EXIT_SAPLVED5_003 User Exit for Tolerances in the Self- Billing Procedure SBINV
 VED50001 EXIT_SAPLVED5_004 Customer-Function for changing invoice data SBINV
 VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
 VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
45. SDPACK
Packing confirmation
 VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
 VMDE0004 EXIT_SAPLVMDE_004 Shipping Interface: Message SDPACK (Packing, Inbound)
46. SDPICK
Picking confirmation
 VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
 VMDE0003 EXIT_SAPLVMDE_003 Shipping Interface: Message SDPICK (Picking, Receipt)
47. SHP_IBDLV_CONFIRM_DECENTRAL
Confirmation (Inbound Delivery)
 V50B0001 EXIT_SAPLV50I_002 User exit for BAPI Verification of Inbound Deliveries
48. SHP_IBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
 V50B0001 EXIT_SAPLV50I_001 User exit for BAPI Duplication of Inbound Deliveries
49. SHP_OBDLV_CONFIRM_DECENTRAL
Confirmation (Customer Delivery)
 V50B0001 EXIT_SAPLV50I_004 User exit for BAPI Verification of Outbound Deliveries
50. SHP_OBDLV_SAVE_REPLICA
BAPI Function Module for Duplication of Outbound Deliveries
 V50B0001 EXIT_SAPLV50I_003 User exit for BAPI Duplication of Outbound Deliveries
51. SHPCON
Delivery: Shipping confirmation
 V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
 V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
 V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
 V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
 V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
 V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
52. SHPMNT
Shipping outbound
 V55K0020 EXIT_SAPLV55K_020 IDoc SHPMNT: Modification Control/ Data before processing
 V55K0021 EXIT_SAPLV55K_021 Processing of segments IDoc SHPMNT
 V55K0022 EXIT_SAPLV55K_022 Update of user defined tables for inbound IDoc SHPMNT
53. SRCLST
Source List
 MMAL0002 EXIT_SAPLMEAI_001 ALE source list distribution: inbound processing segments
 MMAL0002 EXIT_SAPLMEAI_002 ALE source list distribution: inbound processing user defined data
54. SRVMAS
Master data service master
 BASI0001 EXIT_SAPLBASI_001 Userexit IDoc inbound service master: segment
 BASI0001 EXIT_SAPLBASI_002 Userexit IDoc inbound service master: database
55. TPSSHT
Shipping planning system: Transfer planned shipments
 V56I0010 EXIT_SAPLV56I_010 IDoc TPSSHT01: Input of planned shipments: Modification of IDoc segments
 V56I0010 EXIT_SAPLV56I_011 IDoc TPSSHT01: Input of planned shipments: modification of transport tab, processing
 V56I0010 EXIT_SAPLV56I_012 IDoc TPSSHT01: Input of planned shipments: update of own tables
56. WHSCON
Delivery: Stock confirmation
 V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
 V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
 V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
 V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
 V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
 V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
57. WMBBIN
Block Storage Bins
 MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
 MWMIDI04 EXIT_SAPLLIDI_004 Customer enhancement for IDoc WMBBID01
58. WMCATO
Reversal/Reversal request for transfer order
 MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
 MWMIDI03 EXIT_SAPLLIDI_003 Customer enhancement for IDoc WMCAI01
59. WMINVE
Inventory count input
 MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
 MWMIDO09 EXIT_SAPLLMDE_003 Customer enhancement for message WMINVE
 MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
60. WMMBXY
IDoc Report goods movements in IM
 MWMIDO08 EXIT_SAPLLMDE_002 Customer enhancement for message WMMBXY (goods movement) inbound
61. WMSUMO
Move storage unit
 MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
 MWMIDI06 EXIT_SAPLLIDI_006 Customer enhancement for IDoc WMSUID01
62. WMTOCO
Transfer order
 MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
 MWMIDI02 EXIT_SAPLLIDI_002 Customer enhancement for IDoc WMTCID01
63. WMTORD
Transfer order
 MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
 MWMIDO10 EXIT_SAPLLMDE_004 Customer enhancement for message WMTORD (Create TO) inbound
 MWMIDO11 EXIT_SAPLLMDE_005 Customer enhancement for message WMTORD (Create TO) inbound
64. WMTREQ
Create/Cancel transfer order
 MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
 MWMIDI05 EXIT_SAPLLIDI_005 Customer enhancement for IDoc WMTRID01
65. WPUBON
POS interface: Upload sales documents (compressed)
 WPUE0002 EXIT_SAPLWPUE_104 IDoc WPUBON01: prior to inbound processing
 WPUE0002 EXIT_SAPLWPUE_105 Check, whether transaction of IDoc WPUBON01 is compressable
 WPUE0002 EXIT_SAPLWPUE_106 IDoc WPUBON01: processing user segment
 WPUE0002 EXIT_SAPLWPUE_109 IDoc WPUBON01: after to inbound processing
66. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
 WPUE0002 EXIT_SAPLWPUE_130 IDoc WPUFIB01: prior to update
 WPUE0002 EXIT_SAPLWPUE_131 IDoc WPUFIB01: processing user
67. WPUFIB
POS interface: Upload Fin.Acc. interface SRS/POS
 WPUE0002 EXIT_SAPLWPUE_132 IDoc WPUFIB01: prior to inbound processing
 WPUE0002 EXIT_SAPLWPUE_139 IDoc WPUFIB01: after to inbound processing
68. WPUKSR
POS upload cashier data
 WPUE0002 EXIT_SAPLWPUE_120 IDoc WPUKSR01: prior to update
 WPUE0002 EXIT_SAPLWPUE_122 IDoc WPUKSR01: processing user segment
 WPUE0002 EXIT_SAPLWPUE_123 IDoc WPUKSR01: prior to inbound processing
 WPUE0002 EXIT_SAPLWPUE_129 IDoc WPUKSR01: after to inbound processing
 WPUE0002 EXIT_SAPLWPUE_152 IDoc WPUTAB01: prior to inbound processing
 WPUE0002 EXIT_SAPLWPUE_159 IDoc WPUTAB01: after to inbound processing
69. WPUUMS
POS interface: Upload sales data (compressed)
 WPUE0002 EXIT_SAPLWPUE_110 IDoc WPUUMS01: prior to update
 WPUE0002 EXIT_SAPLWPUE_112 IDoc WPUUMS01: prior to inbound processing
 WPUE0002 EXIT_SAPLWPUE_113 IDoc WPUUMS01: processing user segment
 WPUE0002 EXIT_SAPLWPUE_119 IDoc WPUUMS01: after to inbound processing
70. WPUWBW
POS interface: Upload goods movements
 WPUE0002 EXIT_SAPLWPUE_140 IDoc WPUWBW01: prior to update
 WPUE0002 EXIT_SAPLWPUE_141 IDoc WPUWBW01: processing user segment
 WPUE0002 EXIT_SAPLWPUE_142 IDoc WPUWBW01: prior to inbound processing
 WPUE0002 EXIT_SAPLWPUE_149 IDoc WPUWBW01: after to inbound processing
71. WVINVE
Store physical inventory / sales price revaluation
 WVFI0001 EXIT_SAPLWVFI_001 Inbound IDoc store phys. inv.: override Customizing
 WVFI0002 EXIT_SAPLWVFI_002 Inbound IDoc store phys. inv.: process customer segment
IDoc Outbound User Exits
72. ACCONF
Confirmation of IDoc processing from the application
 ACCID002 EXIT_SAPLACC2_040 IDOC ACCONF: Confirmation of processing in application
73. ACLPAY
Accounting: Inbound invoice
 ACCID002 EXIT_SAPLACC2_030 IDoc ACLPAY: Userexit for header in accounting document (outbound)
 ACCID002 EXIT_SAPLACC2_031 IDoc ACLPAY: Userexit for creditor line (outbound) in accounting document
 ACCID002 EXIT_SAPLACC2_032 IDoc ACLPAY: Userexit for general line (outbound) in accounting document
 ACCID002 EXIT_SAPLACC2_033 IDoc ACLPAY: Userexit for tax line (outbound) in accounting document
74. ACPJMM
Posting in accounting from materials management
 ACCID002 EXIT_SAPLACC2_020 IDoc ACPJOU: Userexit Userexit for GL posting header in accounting document
 ACCID002 EXIT_SAPLACC2_021 IDoc ACPJOU: Userexit Userexit for GL posting line in accounting document
75. ARTMAS
Create and change of material master (Retail)
 MGV00003 EXIT_SAPLMV01_003 Enhancement for article master IDoc: Create
76. BLAORD
Purchasing contracts
 MM06E001 EXIT_SAPLEINM_016 ALE distribution of contracts outbound enhancement for IDocs
 MM06E001 EXIT_SAPLEINM_017 ALE distribution of contracts outbound enhancement for IDocs
77. BLAREL
Purchasing contracts
 MM06E001 EXIT_SAPLEINM_003 Customer enhancements of data segment for outbound release documentation
78. COND_A
Conditions: master data for price determination
 VKOE0001 EXIT_SAPLVKOE_001 Condition Transmission: Derivation of Filter Object E1KOMG
 VKOE0001 EXIT_SAPLVKOE_002 Condition Transmission: Customer segments
79. CREMAS
Distribute vendor master
 VSV00001 EXIT_SAPLKD01_001 Outbound: Create vendor segments
80. DEBMAS
Customer master
 VSV00001 EXIT_SAPLVV01_001 Outbound: Create additional customer master segments
81. DELPKB
KANBAN call
 MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
 MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
82. DIRDEB
Preauthorized withdrawal
 FEDI0003 EXIT_SAPLIEDP_003 FI-EDI outgoing payments: Save PEXR segments (customer directory)
83. DOCMAS
Master document
 CVDS0001 EXIT_SAPLCVALE_002 Userexit for ALEDVS (DOCMAS outbound)
 CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
84. DOLMAS
Document-object links
 CVDS0001 EXIT_SAPLCVALE_004 Userexit for ALEDVS (DOLMAS outbound)
 CVDS0001 EXIT_SAPLCVALE_005 Userexit for filter (ALE outbound)
85. FIDCC1
Send entire FI documents (user exit 003/4)
 F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
 F050S002 EXIT_SAPLF050_003 FIDCC1 IDoc outbound: Change data / do not send
 F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
86. FIDCC2
Send entire FI documents (user exit 005/6)
 F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
 F050S003 EXIT_SAPLF050_005 FIDCC2 IDoc outbound: Change data / do not send
 F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
 F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
87. FIDCMT
Sending single items for FI-GL
 F050S004 EXIT_SAPLF050_007 IDoc outbound: change complete IDoc / do not send
88. FIPAYM
Payment data
 FIPAYM01 EXIT_SAPLF11A_001 USER-EXIT: message type FIPAYM, header data, outbound
 FIPAYM01 EXIT_SAPLF11A_002 USER-EXIT: message type FIPAYM, reference data, outbound
 FIPAYM01 EXIT_SAPLF11A_003 USER-EXIT: message type FIPAYM, bank data, outbound
 FIPAYM01 EXIT_SAPLF11A_004 USER-EXIT: message type FIPAYM, GL data, outbound
 FIPAYM01 EXIT_SAPLF11A_005 USER-EXIT: message type FIPAYM, partner data, outbound
89. FIROLL
General ledger rollup for FI-GL (delta f. line items FIDCMT)
 F050S001 EXIT_SAPLF050_001 IDoc outbound: fill user-defined IDoc segment
90. GSVERF
Cred. memo procedure
 MRMN0001 EXIT_SAPLMRMN_001 Outbound IDoc for ERS/consignment settlement
91. HRMD_A
HR: Master data and organizational data (appl. system)
 RHALE001 EXIT_SAPLRHA0_001 HR-CA: ALE outbound processing: Enhancement for receiver
 RHALE001 EXIT_SAPLRHAL_001 HR-CA: ALE outbound processing: Change IDoc
 RHALE001 EXIT_SAPLRHAL_003 HR-CA: ALE outbound processing: conversion info type / segment
92. INFREC
Purchasing info record
 MMAL0003 EXIT_SAPLMEAO_002 ALE purchasing info record distribution: outbound processing
93. INVOIC
Invoice / Billing document
 LVEDF001 EXIT_SAPLVEDF_001 User_Exit controll data IDoc_Output_Invoic
 LVEDF001 EXIT_SAPLVEDF_002 User_Exit customer enhancement of segments outbound invoice
 LVEDF001 EXIT_SAPLVEDF_003 User_Exit to avoid reading package data
 LVEDF001 EXIT_SAPLVEDF_004 EDI Invoice: customer enhancement for reading additional data
94. KANBAN
KANBAN call
 MPKD0001 EXIT_SAPLMPKD_001 User exit for control record KANBAN, outbound
 MPKD0001 EXIT_SAPLMPKD_002 User exit for EDI
95. LIKOND
Listing conditions
 WSOR0001 EXIT_SAPLWSOE_001 Enhancement for assortments: outbound IDoc
96. MATMAS
Material Master
 MGV00001 EXIT_SAPLMV01_002 Enhancement for material master IDoc: Create
97. ORDCHG
Purchase order/order change
 MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
 MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
 MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
98. ORDERS
Purchase order / order
 MM06E001 EXIT_SAPLEINM_001 Customer enhancements for control record: purchasing document, outbound
 MM06E001 EXIT_SAPLEINM_002 Customer enhancements to data segments, purchasing document, outbound
 MM06E001 EXIT_SAPLEINM_011 Final customer enhancement EDI purchase order outbound
99. ORDRSP
Purchase order / order confirmation
 MM06E001 EXIT_SAPLEINM_009 MM EDI ORDRSP: customer enhancements tolerances (quantities/ date/price)
 MM06E001 EXIT_SAPLEINM_014 MM EDI ORDRSP:enhancement price tolerances
 MM06E001 EXIT_SAPLEINM_015 MM EDI ORDRSP: enhancement change of vendor material
 SDEDI001 EXIT_SAPLVEDC_001 Customer enhancement for control record of order confirmation
 SDEDI001 EXIT_SAPLVEDC_002 Customer enhancement for data records of order confirmation
 SDEDI001 EXIT_SAPLVEDC_003 SD EDI ORDRSP: customer enhancement
 SDEDI001 EXIT_SAPLVEDC_004 SD EDI ORDRSP:customer enhancement for reading additional data
 SDEDI001 EXIT_SAPLVEDC_005 SD EDI ORDRSP: customer enhancement for configuration
 SDEDI001 EXIT_SAPLVEDC_006 SD EDI ORDRSP: customer enhancement for configuration structures
 SDEDI001 EXIT_SAPLVEDC_007 SD EDI ORDRSP: customer enhancement for header conditions
 SDEDI001 EXIT_SAPLVEDC_008 SD EDI ORDRSP: customer enhancement for item conditions
 WVFB0001 EXIT_SAPLWVFB_001 Customer exists for store order PO confirmation control seg.
 WVFB0001 EXIT_SAPLWVFB_003 Customer exists for store order PO confirmation data seg.
100. PAYEXT
Extended payment order
 FEDI0003 EXIT_SAPLIEDP_002 FI-EDI outgoing payments: Save PEXR segments (external payments)
 FEDI0004 EXIT_SAPLIEDP_901 FI-EDI outgoing payments: New partner house bank
 FEDI0004 EXIT_SAPLIEDP_902 FI-EDI outgoing payments: End of IDoc payment (VBLNR)
 FEDI0004 EXIT_SAPLIEDP_903 FI-EDI outgoing payments: End of partner house bank
101. PICKSD
Picking data confirmation to customer delivery
 VMDE0002 EXIT_SAPLVMDE_002 Shipping Interface: Message PICKSD (Picking, Outbound)
102. PRDCAT
Product Catalog
 WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
103. PRDPOS
Product catalog item
 WPCI0001 EXIT_SAPLWPCI_001 User exit for Product cat. IDoc outbound
104. PRICAT
Price list / catalog
 VPRE0001 EXIT_SAPLVPRE_001 PRICAT outbound processing (MAMT AUSP MAW1)
 VPRE0001 EXIT_SAPLVPRE_002 PRICAT outbound processing (control record)
 VPRE0001 EXIT_SAPLVPRE_003 PRICAT outbound processing (IDoc segments)
105. PROACT
Stock and sales data
 WVMI0001 EXIT_SAPLWVMI_001 IDoc PROACT outbound: final action prior to sending
106. REMADV
Payment advice
 FEDI0003 EXIT_SAPLIEDP_001 FI-EDI: Outgoing pmnt advice - Create extension of segments/ new segments
107. REQOTE
Inquiry
 VEDE0001 EXIT_SAPLVEDE_001 Customer enhancement for control record of outbound quotation
 VEDE0001 EXIT_SAPLVEDE_003 SD EDI REQOTE: customer enhancement
 VEDE0001 EXIT_SAPLVEDE_002 Customer enhancement for data records of outbound quotation
 VEDE0001 EXIT_SAPLVEDE_004 SD EDI REQOTE: customer enhancement for reading additional data
 VEDE0001 EXIT_SAPLVEDE_005 SD EDI REQOTE: customer enhancement for configuration
 VEDE0001 EXIT_SAPLVEDE_006 SD EDI REQOTE: customer enhancement for configuration structures
 VEDE0001 EXIT_SAPLVEDE_007 SD EDI REQOTE: customer enhancement for header conditions
 VEDE0001 EXIT_SAPLVEDE_008 SD EDI REQOTE: customer enhancement for item conditions
108. SRCLST
Source List
 MMAL0001 EXIT_SAPLMEAO_001 ALE source list distribution: outbound processing
109. SRVMAS
Master data service master
 BASO0001 EXIT_SAPLBASO_001 Enhancement: service master, check standard service catalog
 BASO0001 EXIT_SAPLBASO_002 Userexit IDoc service master: receiver determination
110. SYPART
Partner profiles
 SIDOC002 EXIT_SAPLEDI6_001 CA-EDI, Partner-IDoc: Exit after segment E1EDPP1
 SIDOC002 EXIT_SAPLEDI6_002 CA-EDI, Partner-IDoc: Exit after segment E1ADRM0
 SIDOC002 EXIT_SAPLEDI6_003 CA-EDI, Partner-IDoc: Final exit before sending
 SIDOC002 EXIT_SAPLEDI6_004 CA-EDI, Partner-IDoc: Exit after segment E1ADRP0
 SIDOC002 EXIT_SAPLEDI6_005 CA-EDI, Partner-IDoc: Exit after segment E1ADRE0
 SIDOC002 EXIT_SAPLEDI6_007 CA-EDI, Partner-IDoc: Exit after segment E1EDP13
 SIDOC002 EXIT_SAPLEDI6_008 CA-EDI, Partner-IDoc: Exit after segment E1EDP21
111. TPSDLS
Shipping planning system: Transfer delivery
 V56I0001 EXIT_SAPLV56I_001 IDoc TPSDLS: Modification of delivery header group
 V56I0002 EXIT_SAPLV56I_002 IDoc TPSDLS: Modification of delivery item group
 V56I0003 EXIT_SAPLV56I_003 IDoc TPSDLS: Modification of package data group
 V56I0004 EXIT_SAPLV56I_004 IDoc TPSDLS: Modification of entire IDoc
 V56I0005 EXIT_SAPLV56I_005 IDoc TPSDLS: Modif. of delivery items relevant to shipment
 V56I0006 EXIT_SAPLV56I_006 IDOC TPSDLS: User-defined determ. for location substitution
 V56I0020 EXIT_SAPLV56I_020 IDoc control record modification in interface SD-TPS
112. WBBDLD
Assortment list: Material data
 WBBE0001 EXIT_SAPLWBBI_001 Modification of replenishment list IDoc
113. WMCATO
Reversal/Reversal request for transfer order
 MWMIDO02 EXIT_SAPLLIDO_002 Customer enhancement for IDoc WMCAID01
114. WMINVE
Inventory count input
 MWMIDO04 EXIT_SAPLLIDO_004 Customer enhancement for IDoc WMIVID01
115. WMRREF
Release reference number
 MWMIDO03 EXIT_SAPLLIDO_003 Customer enhancement for IDoc WMRRID01
116. WMTORD
Transfer order
 MWMIDO01 EXIT_SAPLLIDO_001 Customer enhancement for IDoc WMTOID01
117. WP_EAN
POS interface: Upload / Download EAN assignments
 WPDA0001 EXIT_SAPLWPDA_003 POS interface: Modification of IDoc data for EAN references
118. WP_PER
POS interface: Upload / Download person data
 WPDA0001 EXIT_SAPLWPDA_008 POS interface: Modification of IDoc data for person related data
 WPDA0001 EXIT_SAPLWPDA_013 POS interface: Add. Change pt. Analysis for WP_PER
119. WP_PLU
POS interface: Upload / Download material master
 WPDA0001 EXIT_SAPLWPDA_002 POS interface: Modification of IDoc data for material master
 WPDA0001 EXIT_SAPLWPDA_009 POS interface: Add. Change pt. Analysis for WP_PLU
120. WPDCUR
POS interface: Download exchange rates
 WPDA0001 EXIT_SAPLWPDA_006 POS interface: Modification of IDoc data for exchange rates
121. WPDNAC
POS interface: Download products
 WPDA0001 EXIT_SAPLWPDA_005 POS interface: Modification of IDoc data for follow-on items
 WPDA0001 EXIT_SAPLWPDA_011 POS interface: Add. Change pt. Analysis for WPDNAC
122. WPDSET
POS interface: Download set assignments
 WPDA0001 EXIT_SAPLWPDA_004 POS interface: modification of IDoc data for set assignments
123. WPDSET
POS interface: Download set assignments
 WPDA0001 EXIT_SAPLWPDA_010 POS interface: Add. Change pt. Analysis for WPDSET
124. WPDTAX
POS interface: Download tax rates
 WPDA0001 EXIT_SAPLWPDA_007 POS interface: modification of IDoc data for taxes
125. WPDWGR
POS interface: Download material group master
 WPDA0001 EXIT_SAPLWPDA_001 POS interface: Modification of IDoc data for material groups
 WPDA0001 EXIT_SAPLWPDA_012 POS interface: Add. Change pt. Analysis for WPDWGR
126. WPUBON
POS interface: Upload sales documents (compressed)
 WPUE0002 EXIT_SAPLWPUE_102 IDoc WPUBON01: prior to update
127. WTADDI
Additionals
 WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
128. WTADDI_CVB1
Additionals w/o 06
 WTAD0001 EXIT_SAPLWTIP_001 Enhancements to Additionals IDoc
General IDoc User Exits
 ALE00001 EXIT_RBDPROSE_001 Old: exit for converting preproduction system to production
 ALE00001 EXIT_SAPLBD11_001 User exit for the IDOC version changer
 BDMO0001 EXIT_SAPLBDMO_001 Old: Enhancement to the ALE distribution reference model
 KKCD0001 EXIT_SAPFKCIM_001 SAP-EIS: User exit for data compression of sender records (used for IDoc conversion)
 KKCD0001 EXIT_SAPFKCIM_002 SAP-EIS: User exit for data summ. Of summarized records befo (used for IDoc conversion)
===
User exits for Pricing.
1.USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ
2.USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
3.USEREXIT_FIELD_MODIFICATION
4.USEREXIT_FIELD_MODIFIC_KZWI
5.USEREXIT_FIELD_MODIFIC_KOPF
User exits for Sales order
1USEREXIT_DELETE_DOCUMENT
2USEREXIT_FIELD_MODIFICATION
3.USEREXIT_MOVE_FIELD_TO_VBAK
4.USEREXIT_NUMBER_RANGE
5.USEREXIT_SAVE_DOCUMENT
User exits for billing
1.USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
2.USEREXIT_ACCOUNT_PREP_KOMPCV
3USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
4USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB
5.USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
====
Reward if USeful
Thanx & regards
Naren..

ACC_INVOICE_RECEIPT03 inbound processing

Hi,
I am using the idoc ACC_INVOICE_RECEIPT03 idoc to receive invoice information from vendor.
Now im confused as to how to process the incoming IDOC.
Im supposed to park a transaction for each of the IDOC received ie simulate FV60.
How can i do this? What inbound process code should i use? Is there any example?
Right now i have given BAPI as the process code, and trying to correct errors in the IDOC.
Thanks
Siva

Hi Sivasakthi,
When I had a requirement like this I used idoc ACC_DOCUMENT instead. The function to process this idoc was IDOC_INPUT_ACC_DOCUMENT which uses BAPI_ACC_DOCUMENT_POST. The problem with this BAPI was that it posts document. It does not park. There is no standard functions available for the parking.
So, I copied 'BAPI_ACC_DOCUMENT_POST' into 'Z_ACC_DOCUMENT_PARK'. Then I removed the code (I kept the import, export etc intact). And I wrote a BDC (call transaction) to call FBV1 transaction and parked the document.
Then I copied IDOC_INPUT_ACC_DOCUMENT to Z_IDOC_INPUT_ACC_DOCUMENT_PARK and simply changed the function call in the code to call my Z function instead of the bapi. I had to just change the function name in the statement, actually.
Salai.

Error while creating inbound process code

Hi gurus,Iam creating a custom idoc.
800 -> sender
810 -> Receiver
i have completed outbound processing on 800.
On 810, completed following steps for inbound processing.
1.) I have added my Inbound FM in BD51.
2 ) Assigned my FM to Message type and Idoc type in WE57.
3 ) When adding my FM to process code in BD67, it is showing error that
Entry ZSATPC does not exist in TEDE2 - check your entry.
{ zsatpc is my custom process code }.
4) While Creating Process Code in WE42 with options [processing with ale service / Processing
by FM] and saving it is giving error that
" " is not a valid language.
And when I saw help (?) regarding this error, the following text appeared in a window.
Diagnosis
A key with language "" "" was specified for table "EDE2T". This is not a valid language.
This applies to field "LANGUA"
System Response
The system rejects the key.
Procedure
Enter a valid language. This is usually the language you logged on in.
You logged on in language "EN".
Table T002 contains a list of valid languages.
Please solve this error. Give me steps to create inbound process code.
thanx in advance. Hoping replies soon........
Satish.

Dear Satish,
Very peculiar. The language should come from your log on language. Try to login into the system again. Call we42 again and see if it works.
Regards, Rakesh

Inbound Processing With BDC

Similar Messages

Maybe you are looking for