Need API for Credit Memo creation-R12

Hi All,
I am working on R12 Implementation process. I have a requirement for creating the "Credit Memo" using API.
Could you please any one provide the API for Credit Memo creation process.
Thanks,
LSP

Hi,
Please refer the following links:
http://www.betteroracle.com/2012/08/ar-api-create-credit-memo-r12.html
http://easyoracleapps.blogspot.com/2011/08/creating-credit-memos-and-appling-these.html
http://prasanthapps.blogspot.com/2011/05/credit-memo-creation-via-api.html
Googling will help you indeed
Rgds,

Similar Messages

Need to avoid credit memo creation if the value is zero'0'

Hi All,
I want to avoid the creation of Credit Memo if the value is zero, how this can be controlled in SD. Please pore your ideas.
Regards,
Ragu

Hi,
In standard SAP system, Credit memo is created with reference to
1) Credit memo request
2) Return order
3) Invoice correction request.
Before releasing these docs for Credit memo creation, check whether the
value is non-zero.
You can put a billing block(Check credit memo) on these documents if the value is ZERO.
And the billing block will only be removed if the value of the doc is non-zero,and a Credit
memo can be raised from these doc.
Second alternative is to check the value in prior request doc by ABAP enhancement,
and if it zero do not create the request/document.
Thanks ,
Umesh Karane.

User exit for Credit Memo creation

I want to create an IDOC when the credit memo will be created.
What is the name of the user exit where I can write the IDOC generation code ?
Edited by: Alvaro Tejada Galindo on Feb 18, 2008 9:47 AM

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

What is the standard API for Customer Contact creation in R12

Hi All,
What is the standard API for Customer Contact creation in R12. my requirement is I need to create contact against Customer(Person/Organization).
I need to develop pl/sql package for create Contact using the following fields
First name , Last name , Email, Phone no, Ph ext,Mobile no,Contact no,Job title, Job title code,Country,Address1,Address2,Address3,Address4,
City,State,Postalcode.
Please help me.
Thanks,
K.Murugesan

Hi All,
Please update if you have any solution.
Thanks
Maanasa

Posting Key for Credit memo need to change

We are haveing cr 1 and dr 50 posting key for Customer invoice,
for credit memot also same. when we create Credit memo it addsup into revenue which is wrong.
WE need to change posting key for Credit memo(G2 doc type)
please provide Tcode /path for it
Thanks in advance,
-Sam

Hi SAM,
1.Tcode: OB41 for configuring posting key
2. IMG --> Sales and Distribution --> Basic Functions --> Account Assignment -> Revenue Account determination -->
Define and Assign Account Keys.
Reward if useful.
Regards
JACK

How to create On Account Credit Memo in R12.1.3

Hello Experts / Dina,
Oracle claims that there is new feature of creating credit memo On Account can be done by using Oracle Projects billing with R12.1.3 only.
For the same they say that:-
The Interface Invoices to Receivables process creates credit memo as On Account Credit Memo when the following conditions are satisfied:
1> The Allow Over Application option is set to No in Oracle Receivables and the Create On Account Credit Memo option is enabled in Oracle Projects and
2> There is no balance available to adjust on the invoice
But I am not sure where to perform the setup mentioned on line 1 of setting up Create On Account Credit Memo option is enabled in Oracle Projects.
Does anyone know about it ? Is it a profile option or setup on someother screen. Please help.
Thanks
Edited by: oracle_samba on Feb 14, 2013 6:16 AM

Hi Dina,
Any help on this?
I found this info under RCD "ORACLE E-BUSINESS SUITE RELEASE CONTENT DOCUMENT Projects Releases 12.1 and 12.2 (inclusive of 12.0.2 – 12.0.7)"section 3.2.3.1. On Account Credit Memo Creation on page 6.
Thanks
:-)

Vendor Credit Memo creation in SAP via IDOC Interface (Inbound)

Hello Team,
I have a client requirement to create Vendor Invoices & Credit memo via Idoc Interface. Iam using INVOIC02 idoc type for posting Invoices and could able to create the invoice successfully. For credit memo , I'm aware that we can use the same idoc type (INVOIC02) and need to pass CRME value for the segment field BSART.
What i need is a sample Inbound INVOIC02 idoc file for credit memo to identify the required fields for successful credit memo creation.
Regards,
Vijay

Hello Team,
I have a client requirement to create Vendor Invoices & Credit memo via Idoc Interface. Iam using INVOIC02 idoc type for posting Invoices and could able to create the invoice successfully. For credit memo , I'm aware that we can use the same idoc type (INVOIC02) and need to pass CRME value for the segment field BSART.
What i need is a sample Inbound INVOIC02 idoc file for credit memo to identify the required fields for successful credit memo creation.
Regards,
Vijay

Standard Process for Credit Memo & Debit Memos in CRM

Dear all,
What is the standard process for Credit Memo and Credit Memo Creation within CRM Complaint Transaction?
We can successfully replicate Return Items and Replacement Items in ECC Return Order
But I don't know how to process Credit Memo and Debit Memo in ECC.
What are the Accounting Implications takes place once we create and release the credit memo / Debit memo in CRM Complaint Transaction?
How to see the entire document flow?
I can create Credit Memo for a Returned Line Item in CRM without any errors. But I could not see any follow-up transaction or process either in CRM or ECC.
Kindly educate me in this regard. Your suggestions are highly appreciated
Best regards
Raghu ram
Edited by: Raghu Ram on Jun 23, 2010 6:29 PM
Edited by: Raghu Ram on Jun 25, 2010 8:30 AM

Hi suchi,
The following would be very useful to you.
To reduce implementation time for print forms development, SAP has created a set of the most commonly used forms - Preconfigured Smart Forms:
SD: Invoice, Quotation, Contract, Delivery Note, Order Confirmation, Scheduling Agreement, Inquiry, Cash Sales, Picking List
MM: Purchase Order, Request for Quotation, Contract, Delivery Schedule, Good Issue (3 scenarios), Good Receipt (3 scenarios)
FI: Dunning Notice
All can easily adapt these forms to their requirements, saving time and money.
Hope this information has been useful to you.
if you would like to have a smartform of your own i.e a Z or a Y then there is an option to get a sap script copied onto a smartform.
the sap script for the same is -> F140_DOCU_EXC_01
Go to Txn SMARTFORMS and just put the required smart form name in FORM field and then go to the menu bar: Utilities-> Migrate SAPScriptForm and juts type in the Script name which is given above(i.e F140_DOCU_EXC_01 )
I hope this will be an amicable solution.
if helpful pls reward.
Thanks
Venugopal

Problem while doing invoice for Credit memo request

Hi all
I very well known that Out boud Delivery is not needed for Credit memo request but after saving the CMR and when i raise the Credit Memo (VF01) system is showing a error message saying "PGI not done for Outbound Delivery 30047402"
In CMR document type i have set the order related billing and i have removed the billing block also
I have raised the CMR based on Invoice
Kindly help me in this regard
Regards
BMS

Hi Raj Aryan Malhotra, Thanks for ur reply
The setting which u said are already there
The second one that is, change the copying requirement of header to 11. i did this but this time the message was different "The document is not relevant for billing" . After checking the log i could the follwoing info
Client                                                   240
Group Number
Sales Document Number
Item Number of the SD Document         000000
Schedule Line Number                         0016
Counter in Control Tables                     00
Message Identification                         VF
System Message Number                    016
Output Type                                        I
Message Variable 01
Message Variable 02
Message Variable 03
Message Variable 04
Group Type                                         F
Kindly help me to resolve this also
Regards
BMS

Credit Memo Creation - Sold-to-party / Ship-to-party fields

I am trying to create a SD Credit memo document.
From the thread Credit Memo Creation I understand that the BAPI BAPI_SALESORDER_CREATEFROMDAT2 cant be used and instead I gotta use the FM SD_SALESDOCUMENT_CREATE for this purpose.
On this backdrop, I am trying to pass sold-to-party / ship-to-party values into this FM.
But, in the structure SALES_HEADER_IN type BAPISDHD1, I couldnt find the fields to pass these values.
Please advise the name of the fileds/structure where I should pass shiptoparty and soldtoparty values.
In VA01 screen, you could see these fields.
Thanks,
Message was edited by:
Jay
Message was edited by:
Jay

jay,
check the below link for couple of sample codes...
Re: BAPI_SALESDOCU_CREATEFROMDATA, create credit memo request
May be helpful for you
~~Guduri

Regarding rate, sales tax and discounts for credit memo request and returns

Dear ALL,
Rate column is not displaying for credit memo request. suppose credit memo should be given due price diifererence
with referance to billing documnet credit memo request to rised. but if i want to edit rate column is not available.
how vat and discount has to be captured in case of rate diifferance for credit memo.
In case of returns will taxes applicable for returns credit memo
Gl accounts for credit memo same as billing or different GL accounts to be maintained or not
client has the scenario that if credit memo request has been rised for with referance to billing due to rate differance.
If customer returns materilas belongs to same billing. so based on the returns order returns credit memo to be rised .
But how the sap captures exact price of the materila during returns. ie; price modified during credit memo request.
Thanks & Regards
ramesh

HI,
Remove all the other condition types from the procedure and keep only those which you need.
Regards
Abhilash

Asset value for Credit memo

Hi Experts,
I'm new to this forum, Need some help on how the Ordinary depreciation calculated for credit memo.
It is Valuated Goods receipt, asset capitalized before the IR. However, there was a difference in value between GR/IR and the different value automatically got adjusted in APC transaction and also credit memo passed for the difference.
My question here is credit memo value is 2.46 but corresponding depreciation value is 22.14.
Note: It's a Low value asset, useful life is 1 Month. Entire depreciation already posted for GR Value which means more than APC value.
GR value           : 1192.20 -----
APC value         : 1189.74------
Ordinary dep     :   1192.20---
(posted value)
Thanks,

Hi Mukthar,
Thanks for your reply.
However, the credit memo value is only 2.46 USD, depreciation getting reversed each month 2.46 USD and total depreciation reversal value is 22.14 (USD).
Just want to understand the logic behind it.
Thanks,

Why need to link credit memo with invoice

Hi, gurus,
I received an AP invoice valued $2222 and then received a credit memo valued $222 about 1 week later.
Now I need to make payment.
I was told it's good to link credit memo with invoice by entering invoice number in the field "invoice reference" when creating credit memo. But I'm not sure why it's better because system will pick up both items anyway when i entered $ 2000 using f-53 to make outgoing payment.
The only reason i can think of is this link will guarantee that credit memo has the same terms of payment with invoice.
Is there any other good reasons? Any help will be appreciated.

Dear,
We need to link credit memo with invoice against for two obvious reasons
1.. Future tracking of all credit memo i-e if we gave excess credits to vendor then it was against which invoice. This will create linkage and tracking of credit memo with invoice that will be shown in FBL1N .
2..At the end of specific time period ,month or quarter ,its a normal practise to reconcile vendor balance as per SAP ledger to that of vendor's own book. At that time you will need credit memo track also that against which invoice was the credit given.
This all can be achived after posting credit memo with refrence to invoice number. Audit perpective should also be kept in mind. Hope this will help you
Regards

Tables for credit Memo and Purchase order

Hi all,
I need to develop a report to dispaly all the credit memos for the open qty,
My issue that is there any table where we can have information for credit memos and purchase order,
like the input fields is company code,customer number,fiscal year,
hope you understnad,
Please let me know if you need any more information,
Thanks&Regards,
Cghand

Hi
Invoice Verific. table:
RBKP - Document Header: Invoice Receipt
RSEG - Document Item: Incoming Invoice
Regards
Prasanna

BOM explosion for credit memo req,free of charge,returns order types

Hi Gurus,
My client has the following requirement.Sales BOM with header pricing has to be configured for standard order, free of charge, credit memo req, debit memo req, returs order types. I have configured the BOM for standard order(ZOR) successfully, but for credit memo request and other orders its not picking correctly.The component items for the BOM structure is repeating twice.Pleae let me know how to maintain item category determination for credit memo request and other order types.
For credit memo req I have created new item category by copying the G2N and updated the structure scope as A and application SD01.so the new item category is ZG2B and I have maintained the below mentioned determination.
ZCR ERLA ZG2B
ZCR ERLA ZG2B G2N
ZCR NORM ZG2B G2N
Regards,
Hari Challa.

Hi,
That is incorrect.
For sales order, you shoudl have used item category groups as ERLA, LUMF respectively. The resultant item categories will be TAP/TAQ etc. The same kind of configuration should be enabled for Credit memos and others also.
There the item category group will be ERLA, or LUMF
The document type will be CR / RE etc based on the process
Now the resultant item category should be TAP/TAQ or you can even have RENN etc but the property of this IC should be same as TAP/TAQ based on what you are expecting, apart from the standard configurations of a return process. If you do this, then your pricing and items will come up properly.
In specific, you have to look at the BOM configuration of the Item category in the BOM area.
If you need any detail, pls let us know.

Need API for Credit Memo creation-R12

Similar Messages

Maybe you are looking for