POS Inbound processing

Hi,
POS inbound idoc Message Type WPUBON is processed to create Billing document.
I want to know how is the idoc related to Billing document.
I want to use a different billing document type Z*** if the POS inbound has customer information and standard billing document type FP if the POS inbound has no customer info.
Where can I configure this.
Thanks
Barry

Hi Barry,
The postings from POS work in a different way. It will always credit your sales revenue and debit the tender account. If you are thinking of crediting the sales rev and debiting the 'customer account' you may need to try the standard sales order route. I would strongly suggest implementing SAP Retail Store for the same, which is meant for that.
Regards,
Suhail Shaik

Similar Messages

Vendor Consignement with POS Inbound

Hi Gurus
We are currently trying to implement Vendor Consignment stock with some of our Vendors.
However we run a POS system that interfaces with SAP through IDOCs.
We have tried a number of Config settings in these areas but are unable to get the POS Inbound transaction to consume the Vendor Consignment Stock. It is using movement type 251, and does not input the K to indicate the article should be consignment.
Are we missing come crucial config we have missed?
Or do we need to develop our POS system to hold a "consignment" indicator to pass through to the POS Inbound process.
Your helps would be much appreciated.
Thanks
Hayley

Hayley
Which idoc you are using in POS inbound to push the consignment sales? WPUWBW01 is the idoc type used earlier for pushing consignment sales from POS back in to the Retail system. Now all the information will be coming in WPUUMS01 idoc only. Let me explain the steps, simply follow the steps to achieve the consignment stock special indicator in inbound. THERE IS NO ENHANCEMENT REQUIRED
1) Activate Retail consignment processing:
IMG --> Log Gen --> Retail consign processing --> Activate retail consignment processing
2) Define strategies for stock determination
IMG--> Log Gen --> Retail consign processing --> Define strategies for stock determination
3) Define stock determination group
4) Define stock determination rule
5) Define stock determination header table
6) Define stock determination item table (K, F)
7) Define alternate stock determination rules for consign processing
8) Assign stock determination rule in applications (assign mvt types 251, 252 here)
9) Configure automatic posting for KON (consignment payables) and AKO (expense/revenue from consign mat consumption)
For POS inbound,
10) Extension for controlling summarized sales
IMG > SD> POS Interface --> Inbound --> Extension for controlling receipt based sales (you need to tick the 'Vendor consignment' )
The final step is very important,
11) Run the transaction WSSS for each site, this will take care of seperation of stock and this txn must be run before you process the POS inbound.
Now do a Sale txn in POS and process the POS inbound and check the stock.
Cheers
Suhail Shaik
SAP Consulting

Profile for POS inbound

Hi folks,
ma client want to use a Profile for POS inbound but without site data. How i can use the profile in this case?
Thanks for help.
Best regards
Michael

Hi Dirk,
the POS Inbound will only work on an IS Retail System and required that you have a corresponding site set up for each store. The POS inbound process reads the POS Inbound profile from the site data (transaction WE03) during the IDoc processing. If there is no entry in WRF1 for this partner the processing will fail.
So if your client has stores that are implemented as customers but not at customers+site, the POS Interface cannot be used.
Regards Carsten

Parallel Processing Bottleneck in POS Inbound WPUUMS01

Will someone explain what is the objective of BD51, if most IDOCs are processed by SAP 1-by-1 using INPUTTYP = 1.
Parallel processing of WPUUMS01 IDOCs seems to be a case of a movie hall with many ticket counters but only 1 usher! IDOC_INPUT_POS_SALES_ACCOUNT seems to me the bottleneck.
Am I right?
Read carefully the two links on BD51
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6688507d11d18ee90000e8366fc2/content.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/0b/2a6688507d11d18ee90000e8366fc2/content.htm
In SDN IDES the 269 entries in TBD51 are
64 0-Mass processing
170 1-Individual input
35 2-Individual input with IDoc lock in CALL TRANSACTION
Observe vast majority as "1 Individual Input".
After reading Notes 199840 & 118924 mentioned below I implemented small IDOCs and RDBAPP01 parallel processing. But benefit was marginal & disappointing at ~12%.
I checked IDOC_INPUT_POS_SALES_ACCOUNT has INPUTTYP = 1.
I suspect that 0-Mass processing should have given the better performance.
"1" and "2" is for function modules process one IDoc per call.
 is for FMs that use "call transaction method"
INPUTTYP = 0 function modules which process IDocs in packets and good for performance.
 is for FMs that use "direct input method"
IDOC_INPUT_POS_SALES_ACCOUNT is part of Function Group WPUE - POS interface, upload processing which is part of package WPOS. This does not have "call transaction" string nor "bdc".
I read carefully
Note 199840 - POS IDoc inbound dispatcher with locking control is SAP's BP must read
This note says "To achieve a good load distribution in doing so, you should split the large IDocs, which are expensive with regards to processing, according to a defined record length. This mainly affects message types WPUUMS (aggregated sales) .... we recommend splitting a large IDoc into several small IDocs anyway..."
Note 118924 - Parallel processing of IDocs in the POS inbound
"Activate the check box 'parallel posting' in the initial screen of RBDAPP01 and enter the server group defined before.
The system automatically distributes the load to the servers of the server group, and for each Idoc packet it starts a dialog process. For each server all dialog processes except for two can be occupied, therefore always make sure there are enough online processes available."
Looking for comments from IDOCs gurus ....
I spent a huge amount of effort with little to show.
Regards
-jnc

yes i did max performance things on the merging logic now i have to create the idocs in the parallel . can you please help me in wrirting the code of creating idocs in parallel.
thanks in advance.
regards ,
khushi
Edited by: Khushboo Tyagi on Jan 19, 2009 4:24 PM

Inbound Processing : BOM-Position deleted

Hi Experts,
I'm using a self-made program to distribute Material-BOMs and Changes.
To explain the problem, here is an example:
I have the following BOM in the Source system:
BOM 1234.567.890 ( at Day 0 )
-- Pos. 0100 - TEXT - Text-ID
-- Pos. 0110 - STOCK ITEM - 9999.888.888
-- Pos. 0120 - STOCK ITEM - 9898.999.999
I made a Change into this BOM, by adding a new position:
BOM 1234.567.890 ( at Day + 1 )
-- Pos. 0100 - TEXT - Text-ID
-- Pos. 0110 - STOCK ITEM - 9999.888.888
-- Pos. 0120 - STOCK ITEM - 9898.999.999
-- Pos. 0130 - STOCK ITEM - 8888.888.999
Now I want to distribute it.
I send the first version ( Day 0 ) by using 'MASTER_IDOC_CREATE_BOMMAT' with MESCOD = 'CRE' and DATUV / ALE_DATUV = STKO-DATE.
Then I send the "Change" version ( Day + 1) with MESCOD = 'CNG' and DATUV / ALE_DATUV = AENR-DATUV.
In the Target system, the BOM is OK at Day 0. At Day + 1, I see the new position with his change number, but the Text-Position has been deleted ?!?!?!?!?
We are using Text-Objects (ID) into Text-Positions. But in the Target system, we don't have these Objects.
Is it possible that the Inbound Processing for BOMMAT IDoc check if the Text-Object exist, and if not, delete the position ?
Rewards for support. Thanks.
Regards,
David

Hi Gordon,
I've decided to copy Function idoc_input_bommat and to make some modifications and now it works fine !
I think the standard function isn't ok.
Regards,
David

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..

Rack Jobber for POS Inbound

Dear Experts,
I would like to ask about POS Inbound for Rack Jobber. SAP said that we can differentiate Revenue Account (GL Account) for each Rack Jobber by adding Vendor in Revenue Account Determination. However, during POS Inbound (Sales Per Receipt or Aggregated Sales), I cannot find the field in IDOC structure to add the vendor value.
Please share me your experience on it.
Thanks.

Dear SAPVN
I am not sure which business scenario are you using rack Jobber for. But from ECC 6.0 onwards, you should user Retail Vendor Consignment process in case you need to handle consignment processing. In such a case you need to maintain settings of Retail vendor Consignment along with a consignment Info record and SD account determination settings which can do the trick.
Hope this helps
regards
Manish

Adding Cost of Sales for Non-Stock articles to POS Inbound Pricing Schema

Hi guys
I'm working on a requirement to derive the Cost of Sales for non-stock items by pulling the current cost for the site and multiplying it by the billed quantity on VBRP. We could create a new condition type using purchase org, article and site in the condition table and manually enter condition records. However it would be more elegant to copy prices from the Purchasing list or deal prices into new condition types in the POS inbound pricing procedure. However SAP standard doesn't seem to allow condition copying from purchasing to sales.
Regards
Brett

Hi ,
As it happens you need to do this for Non-Stock Articles only.... then you need a routine to do this .
And then in IS -Retail do we not use NETPrice or Final Cost Price to derive the Sales Price ... In that case you get the Cost Price when the Billing doc is getting posted at line level...
Regards
Amitava

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

Article with Batch management in POS Inbound

Dear SAP Experts,
I encountered problem for POS inbound for articles that activated Batch Management in SAP Retail. The system always send error message to require the batch, however, I cannot give SAP the batch number I want to update the stock by using POS inbound (both aggregated sales and sales per receipt). I cannot find any IDOC type that support that.
I don't know whether SAP Retail supports batch management for article or not. In case they support it, how can we do the POS inbound for the articles.
Hope to get your supports,
Thanks in advance,

hi,
"Batch management requirement cannot be changed" -
Once the material is made relevant for batch -by putting a tick in any of the relevant views in material master -it cannot be changed again if any delievry / stock is already maintained for that material.

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.

BPM Error Permanent Error in BPE inbound processing

Hi
I require some urgent help on this BPM issue.
We are trying to integrate SRM PO being directly sent to Vendors using HTTP. We are getting an error saying Permanent Error in BPE inbound processing. The scenario works like this.
SRM system would sent PO using the SRM Standard interface PurchaseOrderRequest_Out. We need to transform the message into cXML format and send it to the vendors using HTTP adapter. Using the HTTP response we need to trigger an email to the business process team.
The SRM interface is under the software component SAP SRM Server 5.5 and our mapping is being done in a common software component and for the vendor interface we have another software component. We have created a relationship in the SLD by making the common SWC as dependent software component to SAP SRM Server and Vendor Software Component. So in the integration repository we are able to get the interfaces for the SAP SRM Server and Vendor Software Component under the common software component. The receive step for this BPM is a copy of the standard SRM interface PurchaseOrderRequest_Out(as the standard interface is an asynchronous interface) and we would require an abstract interface for the BPM. We have checked the semantics for the BPM and its fine. The related ID development is in place. When the message is being triggered, it gives us this above mentioned error. When we go to the QRFC monitor we are able to check the details.
Regards,
Indranil

Hi Indranil,
 You don't see you BPM....
First go to SXI_CACHE and check that your BPM is listed there and that the compilation has been completed succesfully.
Is this the first time the BPM is being used? If so check if has been configured. For example, go to RWB->Component Monitoring->BPE in <SYSID>
and check if any error is listed there.
In order to check what is going on in your BPM you can trace it:
 SXMB_MONI_BPE->Diagnosis Processes with Errors
 SXMB_MONI->Process, get your msg and click on 'PE'. You should see the workitems and see if there is any error.
 Hope this helps you....
 Regards,
 Encinas.

IDOC failure in R/3 Inbound processing

Hi
I was able to successfully generate XML files from Syndicator, but when it comes for processing in R/3 side it get fails all the time with the IDOC err msg : "IDoc included in IDoc packet containing an error: transfer it separate ".
Kindly adivce how to solve the same.
thanks in adv
Alexander

Hi Ravi
Let me explain in detail.
From R/3 to MDM --> All materials in one XML file.
while from MDM to R/3 --> 3 diiferent IDOC am able to
see, one for each material in Inbound Processing.
kindly advice me how to fix the same.
thanks
Alexander

Steps in Inbound Processing in ALE IDOC

Hi all,
Could anyone explain the steps to be followed in inbound processing in ALE Idoc.
I know we have to create a FM n then call that in a program. But still the detail steps are not clear.
An example will be really helpful.
Thanx

Hi
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
Check these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Reward points for useful Answers
Regards
Anji

Permenant error in bpm inbound processing error in inbound queue of pi7.1

Hi Experts,
In E filling scenario in SAPPI7.1, iam facing a problem. i.e In sxmb_moni message monitoring, the message was schedule at outbound side.when i extend that, the message was stuck in smq2 with "permenant error in bpm inbound processing".can any one please tell me how to relove this issue.
Thanks & Regards,
Giri.

Hello
Check the note #1126656 BPE-TS: Permanent errors in the BPE inbound processing. This describes some possible causes and solutions for this error.
Regards
Mark

POS Inbound processing

Similar Messages

Maybe you are looking for