Goods Return or AP Credit Memo Creation if AP Reserve Inv created

Hi All,
Can anyone tell me how to create good return or ap credit note if ap reserve invoice is used. GRPO created with reference to ap reserve invoice always closed.
Regards

Hi,
We cannot create neither Goods Returns based on GRPO which is based on A/P Reserve
Invoice, nor Credit Memo based on A/P Reserve Invoice on which GRPO is
based.
To cancel GRPO based on A/P Reserve Invoice, create Goods Returns NOT
based on any document whith exactly the same data as in GRPO that should
be cancelled. Next, Copy this return to AP Credit memo.
If you have created a payment based on AP reserve invoice, cancel it, it should reopen the AP reserve invoice document status in 2007 A. Then you can easily create AP credit memo.
Please try in test environment first.
Regards
Preety Goel
SAP Business One Forums Team

Similar Messages

Goods Return and MIRO Credit Memo

Hello Friends,
Please give your suggestions for the queries below :
1. Is there any way we can create Credit Memo (MIRO) with reference to MIGO 122 Movement document (Rejected material returned)
2. Is there a report that shows the list of MIRO Credit Memos. (My document type is the same for both Invoice and Credit Memo)
3. Is there a standard report of MIGO 122 Movement document linking with MIRO Credit Memo and possibly PO.
4. If 161 movement solves my problem, what is the document that I can print out and send alongwith the rejected material to Vendor.
The question from my customer that how do confirm whether credit memo have been entered for all that is moved out of their premises as rejected material.
Regards

Hi,
1. If you are using ERS, then running MRRL transaction will automatically generate credit memo for your return delivery with movement type 122.
2. MIR5 is the one you should look into.
3. Take a look into ME80FN report. Yet, this report does not indicate specifically for movement type 122. If it is required that this movement type shall be chosen as part of selection parameters, then you should develop your own report.
4. There is not any particular difference if you are using movement type 161. The only difference is that in case of using 161, you will have to raise a new return PO and make necessary GR and IR posting. However, the disadvantage is that you will lose the track of your original PO (and PO history).
Cheers,
HT

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.

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

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,

Multiple credit memo creation for single credit memo request

Hello,
The problem is that I am able to repeatedly create multiple credit memos for the same credit memo request. The system is not stopping me by saying "This order is fully invoiced".
I observed the following in the customizing:
1. If the sales document category of the billing document (in VOFA transaction) is 6 (Intercompany credit memo), then I am able to create mulitiple credit memos against the same credit memo request.
2. When I change the sales document category of the billing document to O (credit memo), then the system stops me from creating multiple credit memos against the same credit memo request.
If I want to maintain 6 (intercompany credit memo) in VOFA and still want the system to stop me from creating multiple credit memos for the same credit memo request, then is there is any other customizing to achieve this?
Thanks,
Shankar

Shankar, most likely the billing status of your sales document is not updated. We have experienced the same (or similar?) issue with the intercompany documents and SAP refused to correct it. Here is a fragment of my message exchange with the SAP support:
We have already read the notes 63459 and 308989. They both do not apply
to our business process. The document flow mentioned in the notes is as
follows:
Sales order - customer billing document - intercompany billing document
Our document flow is different:
Contract - customer billing document - Intercompany sales order (could
be more than one order per customer billing document) - intercompany
billing document
The order-related billing status is not being updated on the
Intercompany sales order.
The process described in the notes implies one-to-one relationship
between the customer and inter-company billing documents and the sale
from a Plant that is assigned to another company. We are in the service
industry and sometimes the sale revenue has to be shared by 2-4
companies within our enterprise.
Good day. It is a standard system behaviour that if the billing document type has SD document cateogry '5' (field TVFK-VBTYP in transaction
VOFA). So it is an intercompany billing.
The order-related billing status VBUP-FKSAA is not affected by the
intercompany billing.
So its billing status remains opened, and can be billed more times.
This doesn't seem right to me. Maybe if more customers complain, they will do something about it.
To some extent this may be managed with copy requirements (VOFM), where you can prevent copying the credit memo line items that have been invoiced. However, this might still lead to the blank documents with 0 value, statuses won't be correct and in VF04 you would see the documents as not invoiced.
I had to do a core modification to resolve this issue in our system. In LV45P011 include I did the following:
* Faktura
*{ REPLACE DC6K903001 1
*\ IF vbfa-vbtyp_n CA vbtyp_fakt AND vbfa-vbtyp_n NA vbtyp_fkiv.
IF vbfa-vbtyp_n CA vbtyp_fakt.
*} REPLACE
Hope this helps.
Edited by: Jelena Perfiljeva on Nov 14, 2008 11:09 PM

Update Billing Document During Credit Memo Creation

Hi,
I need to update the billing document during credit memo creation in VA01. Is it possible to achieve this requirement since the billing document is in use during the runtime?
Thanks & Regards,
Mawi

Hi Mawi,
When you are trying to change billing document use CALL FUNCTION 'DEQUEUE_ALL'. It will unlock that billing number and you can change that billing document.
Thanx & Regards
Rami Reddy

Re: Credit memo creation - Update terminated

Hello
I have a issue related to Credit memo creation.
When i try to create a Credit memo with reference to Credit memo request, below error is appearing.
Express error - Update was terminated
Error info - TD465: device type ZHPLJCM1
Credit memo number is getting generated but when i go to view mode (VF03) there is no credit memo in the database.
Even in table VBRK, no data is available.
Could you please suggest how to resolve this issue.
thank you
Anirudh

Hello,
Goto Transaction code SM13 and clilck on the ALL option in Status and Execute.
Then it will lead to the next screen where you have option of MODULES, click on it and and it will give the Program and Technical data.
Clearly it will give the details where the problem lies, Work with your ABAPER and fix.
Regards,
santosh

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

Return order and credit memo request

Hi SD guru,
If goods returned by the customer then what is the appropriate sales order type i should use means whether i have to create the credit memo request or return sales.
Please elaborate both scenarios where exactly i can use sales order type return and credit memo request.
Thanks
saj

hi sajid
when ur creating the Return order use the doc type RE in standard
followed by return delivery LR adn billing ths nothing but the creditmemo.
if your supposed to just adjust the values . then use the G2 credit memo request , with reference to the billing doc for which ur intending to issue the credit memo,and credit memo by billing the same .
hope this answers your question
reward if helped
regards
giri

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

Error in Credit Memo Creation using BAPI

Hi,
While creating a Credit memo using the BAPI "BAPI_SALESDOCU_CREATEFROMDATA" , the following message is returned: "EVP 113Processing customer 9012041 terminated"
This occurs only for a particular customer, while for others the BAPI works fine.
I tried to create a Credit Memo using VA01 for the above customer. The Credit Memo got created there.
I am not able to find out a reason for the above. Can anyone help me with this.
Thanks in advance,
Amit

Hi,
Check the dump in SM14 and see where exactly it is throiwng error..Put a break-point before that and then debug the bapi and see if ur missing anything for this customer and what is the difference between this customer and other customer data.
Regards,
Nagaraj

Amount to credit greater than credit balance - goods return to AP Cred Note

Hi All,
I've got the following scenario:
We have a AP Goods Return on the system which totals £12.94 with freight charges of -£3.75. We have copied this to a AP Credit Note, but have amended the freight from -£3.75 to -£3.00(UK VAT Rate 15% applicable throughout). The total credit field now shows £13.80 and the credit balance field shows £12.94. When you try to add the document it gives an error "amount to credit greater than credit balance". I'm using 2005A PL53.
Can anyone please advise the reason behind the error and also what the correct way of handling this kind of transaction would be?
Kind regards,
Matt

Hi Wesley,
I tried both methods and it doesn't resolve the issue. Spoke to SAP, they gave me a solution and workaround, the issue is a bit more complicated as what it may seem. You manually have to close the goods return, create a standalone service credit note with the appropriate GL account to reverse out the "goods clearing account" entry created by the reversal journal. The bahaviour has been changed in SBO 2007 and therefore the problem is not present in this version anymore. Thanks for your help anyway.
Kind regards,
Matt
Edited by: Greeff Matt on Jun 5, 2009 9:47 AM

Copying Goods return to AP Credit note

Hi all,
We've returned some goods to a supplier, so we do a goods return on SAP, so that credits stock and Debits allocation account.
Our supplier has sent us an AP credit note. So we 'copy to' AP Credit (from Goods return) and the automatic journal entry is Credit Allocation account Debit Accounts payable.
My question is, all of the above entries are balance sheet entries. Shouldn't a goods return have some 'income' effect on the P&L?
Thanks for any help...

When you make good return
Then
Goods Receipt Not Invoice   Debited(Liability )
Inventory Account                Credited(Asset)
And when you make A/P Credit note based on Good Return,
Vendor Account                     Debited(Liability)
Tax Account                           Credited(Asset)
Goods Received Not Invoice Credited(Liability)
so i think ,there are not any ledger belong from P & Loses .
Thanks
manvendra

Sales Return Process-Invoice(Credit Memo) with ref. to delivery

Dear All,
I am doing sales return process.
Sales Order-RE
Delivery-LR
Invoice-RE,
with ref. to sales order it is allowing me to create invoice.
But,with ref. to delivery it is not allowing.
It is giving "The document is not relevant for billing".
I have changed item category REN for delivery (A) related billing.
Also changed req. copy control setting.
Can anybody guide on this issue.
Best Regards
Sainath

Hello,
Normally return credit memo will be generated with reference to the retrun order, and that is the standard SAP process. Do you have any specific requirements to have the credit memo with reference to a retrun delivery?
The Item category REN Billing Relevence will be B as per SAP standard, if you wish to have a delivery related credit RE, the make this to A .
Maintain the Delivery to Billing Copying control in VTFL for LR --> RE, add the item categroy REN.
Maintain the copying requirements for header as 3 Header Del Rel and for item as 4 Deliv-Related item .
Once these setting are done, then check whether the RE billing type is triggering from LR?
Prase

Goods Return or AP Credit Memo Creation if AP Reserve Inv created

Similar Messages

Maybe you are looking for