CREDIT MEMO OUTPUT TYPE !

I got a stuff in www.**************** where they have used NEU as message type / output type in case of automatic idoc generation when PO is created or changed.
I have a requirement for automatic idoc generation when credit memo is created...i have selected application V3 ..in NACE
What will be the output type here ?

check this link. it has given how to set output type for pdf/smart form, I think same output type need to be used but for Idoc type GSVERF
http://help.sap.com/bp_bblibrary/500/Documentation/G93_BB_ConfigGuide_EN_US.doc
In this step you define a Output Determination Procedere for the Billing Documents (Credit Memos) creating on Sales return Process.

Similar Messages

A/P Credit Memo (Item Type) not to deduct quantity in inventory

Hi,
1. I purchased an item > supplier gave me invoice> I key in A/P Invoice (Item Type)
2. Found out item was overpriced
3. Supplier gave me Credit Note to adjust the price
How do I key in this credit note via A/P Credit Memo? To my understanding if I key in the a/p credit memo (item type), my inventory quantity will be deducted as well.

Because the item is over priced, it means that my inventory gl is over stated. When I get the supplier's CN, I will have to reduce the inventory gl. When I create a Service Type A/P Credit Memo I must choose inventory gl. But this will create another problem - Inventory Audit Report balance will not tally with Inventory gl balance (because i didn't reduce the item price in the first place). To solve this is to do a Inventory Revaluation.
Hi Lay Chin, what you suggested is the best option so far.
Thank you everyone for the reply.

Getting split payment terms in case of customer credit memo(Doc type DG)

Hi Guys,
Is there any FM available for getting split payment terms in case of customer credit memo(Document type DG). There will be no invoice/billing doc for this document type and will be created from FB75 transaction. For billing document i am using FM SD_PRINT_TERMS_OF_PAYMENT_SPLI. Please let me know if there is any FM for accounting document also.
Thanks,
Vinod.

Hi,
Try this bapi
BAPI_AR_ACC_GETSTATEMENT

BAPI to park Debit Note (Vendor credit memo) Doc Type: 'KG'

Hi All,
A friend of mine desperately needs to know any BAPI for parking Debit Note (Doc.type : KG Vendor credit memo)... Please let me know if you know about any BAPI / Funcation module to do it and a little chunk of sample code will surely help me a lot....
Thanks in Advance,
Regards,

Hi Savitha,
Well, we have experiemented with this BAPI "BAPI_INCOMINGINVOICE_PARK" earlier, but we found out that it dose not work properly for Service Orders; also it dose not seem to post proper debit note. Anyways, we have used another BAPI "BAPI_ACC_GL_POSTING_POST", it worked but it posts the debit note (Vendor Credit Memo) but we only want to park the debit note and let the user review it and then the user can post it manually or so afterwards...
Regards,
Athar

Credit Note output Type

Hi,
how to configure the output type for credit note?..what are the steps to achieve this??..
Here the form is a z type,not the standard one.
Thanks
Sri

Hi
The correspondence type is maintained in OB77 say SAP11
For this correspondence type you can maintain your Zprogram and variant in OB78
Save the variant for the above program, by running the program in SA38
Thank You,

EDI billing outputs are capturing credit memos as well as invoices

I am a newcomer to the company I am currently with, and to this forum, and I have 6 years of experience in EDI and SAP SD.
I am working on a project to determine why our EDI billing outputs are capturing credit memos as well as invoices, and attempting to send them by EDI, causing failures in our Seeburger translator. Most customers donu2019t want credit memos by EDI. My goal is to track backwards and determine what portion of the EDI process in SAP is pulling credit memos rather than just invoices. I suspect that someone intentionally made changes in the past to put this in place, but we need to have a message type that includes invoices and credit memos, to be attached to specific partners that want this, and another more standard message type that sends only invoices.
The message control for the example partner specifies Message Type ZURH (customized by this company for some reason), Application V3 (which seems standard), and process code SD09 (which seems standard). Could someone help me to navigate to an area where I may be able to find out what parameters are used to determine what transaction types are pulled to be sent out by EDI for billing? I suspect that the issue may be in Application V3, but I am unable to find any help to view u2018Applicationsu2019, because application is such a widely used word.
How can I display/change Application V3, in order to check itu2019s contents?
Any other ideas why credit memos may be included would be appreciated, and I always appreciate having the transaction codes mentioned as well.
Thank you in advance for your assistance.
Application V3 (what specifies what transaction type this pulls?)
Message Type ZURH,
Process Code SD09.
Access Sequence used is ZSD1 Billing Documents (Access Sequence ZSD1 does not appear in transaction V/48 (?))
Transmission Medium is 6 EDI.
The program is RSNASTED, and the FORM Routine is EDI_PROCESSING.

Satish,
Thanks for the suggestions.
I checked transaction VV33 u201CDisplay Output Condition Records: Billingu201D for Output Type ZURH, Key Combination Sales Org/Payer, and I find the example customer linked to ZURH, as I would expect (5010013645     BEST BUY CANADA Vendor #41448     PY          6     1).
I donu2019t see any data about specific transaction types such as credit memos or invoices, so I may not be looking in the right place. I donu2019t find entries under any other key combination. How would I check if Output Condition records are maintained for credit memos?
In regards to the output type being assigned to the credit memo billing type (ZG2U), Iu2019m afraid I donu2019t know how to check that either.
In NACE, I see that u2018Proceduresu2019 list the CTyp (?), and procedure US0001 is the only one that includes credits and debits. I donu2019t recognize the Ctyps ZDN0 and ZCN0. The billing type is ZG2U, which I don't see in any of the Procedures:
10     1     RD00     Invoice
20     2     ZPRO     Proforma Invoice
30     1     ZCAN     Canadian Cust. Inv
40     1     ZCOM     Commercial Invoice
50     1     ZDN0     Debit Note
60     1     ZCN0     Credit Note
How would I be able tell which u2018Procedureu2019 is being used for Application V3, and how would I change that to another Procedure for testing?

SAP 1099 - not showing credit memo - KG doc type

Hello,
When i run the generic w/h report for 1099, it is not showing credit memo , KG doc type .
The vendor is flagged for 1099 and also the KG doc contains the W/H base and tax code .
please let me know .
thanks very much.

Hi,
I am sorry, the note is not releasead yet. I will let you know when it would be.
Meanwhile, please check if the hints below resolves your issue:
Please run the S_P00_07000134 report (RFIDDYYWT ) with option of 'Further Selection' 'Credit Memo Doc. types' Technical name of P_CMDCTY with value of KG then desired result will show.
with Additionally
please refer the note no 945664
MANUAL ACTIVITIES:
1. Goto trasaction se38
2. Give the program name as 'RFIDYYWT'
3. Click on Goto->Text Elements->Selection Texts on the Menu bar
4. Goto editable mode.
5. Search for parameter 'P_CMDCTY'. Specify the selection text as
'Credit Memo Doc. types'. Uncheck the adjoining checkbox for Dictionary
ref.
6. Activate the changes.
I hope it helps.
Best Regards,
Vanessa Barth.

Credit memo print preview problem

Hi Friends,
The present process is return sales , in which return sales order created with reference to sales order, Credit memo request created and Credit memo also created.But the problem is not getting print preview.Error message is Excise invoice corresponding to the document type is not found.
We are generating Excise invoice Automatically, Is there any effect of this on the present issue.Please give some hint.
Thanks
Chetan

Hi,
See normally we have excise invoice creation automatic when invoice is saved. In such cases we have a check in the print program of invoice, which prevents its printing if excise invoice is not created.
In case of credit memo, you might not be creating any excise invoice, but the print program attached might be preventing its printing also.
Check that such a check is given in print program for credit memo output, if yes you may have to remove it.
Hope this helps you.
Regards,
Dhananjay

Credit Memo API AR_CREDIT_MEMO_API_PUB.CREATE_REQUEST end with error,

Hey Guys,
I have to create credit memo for invoice but the api API AR_CREDIT_MEMO_API_PUB.CREATE_REQUEST end with the following error.
Error Calling arp_process_header.post_commit ORA-20001:
Failure encountered in AR_CREDIT_MEMO_API_PUB.Create_request call to arw_cmreq_cover.ar_request_cm
My environment detail are following
Database : Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
Application : 12.0.6
Patch Level - R12.AR.A.6
Kindly help me its urgent bases
Regards
Mazhar Hussain

The code is following
CREATE OR REPLACE PACKAGE BODY DMAPAR03_PVT AS
NAME: DMAPAR03_PVT
PURPOSE: CREATING CREDIT MEMO FOR INVOICES
REVISIONS:
Ver Date Author Description
1.0 29-Dec-2011 MAZHAR HUSSAIN 1. Created this package.
PROCEDURE CREATE_CM(
ERRBUF OUT VARCHAR2,
RETCODE OUT VARCHAR2,
P_ORG_ID IN NUMBER,
P_TRX_TYPE IN NUMBER,
P_TRX_NUM_FR IN VARCHAR2,
P_TRX_NUM_TO IN VARCHAR2
IS
V_TRX_DATE DATE := '31-AUG-2011';
CURSOR C_TRX
IS
SELECT TRX.TRX_NUMBER, TRX.CUSTOMER_TRX_ID, RS.CREDIT_MEMO_BATCH_SOURCE_ID CM_SOURCE,
NVL (SUM (TL.EXTENDED_AMOUNT), 0) LINE_AMT,
(SELECT NVL (SUM (L.EXTENDED_AMOUNT), 0)
FROM RA_CUSTOMER_TRX_LINES_ALL L
WHERE L.CUSTOMER_TRX_ID = TRX.CUSTOMER_TRX_ID
AND L.LINE_TYPE = 'TAX') TAX_AMT, RS.NAME SOURCE_NAME,
RS.DEFAULT_INV_TRX_TYPE DEF_TRX_TYPE, TYP.NAME TRX_TYPE_NAME,
RS.BATCH_SOURCE_ID, TYP.CREDIT_MEMO_TYPE_ID
FROM RA_CUSTOMER_TRX_ALL TRX,
RA_CUSTOMER_TRX_LINES_ALL TL,
RA_CUST_TRX_TYPES_ALL TYP,
RA_BATCH_SOURCES_ALL RS
WHERE 1 = 1
AND TRX.TRX_NUMBER BETWEEN NVL (P_TRX_NUM_FR, TRX.TRX_NUMBER)
AND NVL (P_TRX_NUM_TO, TRX.TRX_NUMBER)
AND TRX.CUSTOMER_TRX_ID = TL.CUSTOMER_TRX_ID
AND RS.BATCH_SOURCE_ID = TRX.BATCH_SOURCE_ID
AND TYP.CUST_TRX_TYPE_ID = TRX.CUST_TRX_TYPE_ID
AND TYP.TYPE != 'CM'
AND TYP.CUST_TRX_TYPE_ID = P_TRX_TYPE
AND TRX.TRX_DATE <= V_TRX_DATE
AND TL.LINE_TYPE = 'LINE'
AND TRX.ORG_ID = P_ORG_ID
AND NVL (TRX.ATTRIBUTE7, 'N') != 'Y' --PREVENT DUPLICATE IMPORT
AND TRX.ATTRIBUTE2 IS NOT NULL ------ MIGRATION REP
GROUP BY TRX.TRX_NUMBER, TRX.CUSTOMER_TRX_ID, RS.NAME, TYP.NAME,
RS.DEFAULT_INV_TRX_TYPE, RS.CREDIT_MEMO_BATCH_SOURCE_ID,
RS.BATCH_SOURCE_ID, TYP.CREDIT_MEMO_TYPE_ID
ORDER BY 1 ;
V_MSG_COUNT NUMBER;
V_MSG_DATA VARCHAR2 (2000);
V_RETURN_STATUS VARCHAR2 (1);
V_REQUEST_ID NUMBER;
V_CM_REASON VARCHAR2(100) := 'A/R ERROR';
V_DUMMY VARCHAR2(240);
V_CM_TRX_NUM RA_CUSTOMER_TRX_ALL.TRX_NUMBER%TYPE;
V_CM_TRX_ID RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID%TYPE;
V_TRX_SOURCE VARCHAR2(100);
V_ORG_NAME VARCHAR2(100);
BEGIN
-- DBMS_SUPPORT.START_TRACE;
BEGIN
SELECT NAME INTO V_ORG_NAME
FROM HR_OPERATING_UNITS
WHERE ORGANIZATION_ID = P_ORG_ID;
END;
IF UPPER(V_ORG_NAME) LIKE 'CN003 (OU)'
THEN
V_TRX_SOURCE := 'CN003_CM_MIGRATION';
ELSE
V_TRX_SOURCE := 'CN001_CM_MIGRATION';
END IF;
FND_GLOBAL.APPS_INITIALIZE
(USER_ID => FND_PROFILE.VALUE('USER_ID'),
RESP_ID => FND_PROFILE.VALUE('RESP_ID'),
RESP_APPL_ID => FND_PROFILE.VALUE('RESP_APPL_ID'),
SECURITY_GROUP_ID => 0
MO_GLOBAL.SET_POLICY_CONTEXT ('S', P_ORG_ID);
ARP_GLOBAL.INIT_GLOBAL;
FOR C_TRX_ROW IN C_TRX
LOOP
/*F P_TRX_TYPE <> NVL(C_TRX_ROW.DEF_TRX_TYPE, -1)
THEN
FND_FILE.PUT_LINE (FND_FILE.OUTPUT,'Default Transaction Type Not Defined
or Not Match with Invoice Transaction Type on Transaction Source: '
||C_TRX_ROW.SOURCE_NAME);
EXIT;
ELSIF
*/ IF C_TRX_ROW.BATCH_SOURCE_ID <> NVL(C_TRX_ROW.CM_SOURCE, -1)
THEN
FND_FILE.PUT_LINE (FND_FILE.OUTPUT,'Credit Memo Batch Source Not Defined
or Not Match with Invoice Transaction Source on Transaction Source: '
||C_TRX_ROW.SOURCE_NAME);
EXIT;
ELSIF C_TRX_ROW.CREDIT_MEMO_TYPE_ID IS NULL
THEN
FND_FILE.PUT_LINE (FND_FILE.OUTPUT,'Credit Memo Transaction Type not Assigned on
Invoice Transaction Type : '||C_TRX_ROW.TRX_TYPE_NAME);
EXIT;
ELSE
BEGIN
AR_CREDIT_MEMO_API_PUB.CREATE_REQUEST
(P_API_VERSION => 1.0,
P_INIT_MSG_LIST => FND_API.G_TRUE,
P_COMMIT => FND_API.G_FALSE,
P_VALIDATION_LEVEL => FND_API.G_VALID_LEVEL_FULL,
P_CUSTOMER_TRX_ID => C_TRX_ROW.CUSTOMER_TRX_ID,
P_LINE_CREDIT_FLAG => 'N',
P_LINE_AMOUNT => -C_TRX_ROW.LINE_AMT,
P_TAX_AMOUNT => -C_TRX_ROW.TAX_AMT,
P_CM_REASON_CODE => V_CM_REASON,
P_SKIP_WORKFLOW_FLAG => 'Y',
P_CREDIT_METHOD_INSTALLMENTS => NULL,
P_CREDIT_METHOD_RULES => NULL,
-- P_BATCH_SOURCE_NAME => C_TRX_ROW.SOURCE_NAME,
P_BATCH_SOURCE_NAME => V_TRX_SOURCE,
P_ORG_ID => P_ORG_ID,
P_DISPUTE_DATE => V_TRX_DATE,
-- P_TRX_NUMBER => 'CM-'||C_TRX_ROW.TRX_NUMBER,
X_REQUEST_ID => V_REQUEST_ID,
X_RETURN_STATUS => V_RETURN_STATUS,
X_MSG_COUNT => V_MSG_COUNT,
X_MSG_DATA => V_MSG_DATA
FND_MSG_PUB.COUNT_AND_GET (P_ENCODED => FND_API.G_FALSE,
P_COUNT => V_MSG_COUNT,
P_DATA => V_MSG_DATA
DBMS_OUTPUT.PUT_LINE ('Return Status ==> ' || V_RETURN_STATUS);
DBMS_OUTPUT.PUT_LINE ('Credit Memo request_id ==> ' || V_REQUEST_ID);
DBMS_OUTPUT.PUT_LINE ('V_msg_count ==> ' || V_MSG_COUNT);
-- FND_MESSAGE.RETRIEVE (V_DUMMY);
DBMS_OUTPUT.PUT_LINE('Error in Create Credit Transaction:'
|| SUBSTR (SQLERRM, 1, 80)||' -- '||V_DUMMY
-- FND_FILE.PUT_LINE (FND_FILE.OUTPUT,'Return Status ==> ' || V_RETURN_STATUS);
-- FND_FILE.PUT_LINE (FND_FILE.OUTPUT,'Credit Memo request_id ==> ' || V_REQUEST_ID);
-- FND_FILE.PUT_LINE (FND_FILE.OUTPUT,'V_msg_count ==> ' || V_MSG_COUNT);
IF V_RETURN_STATUS = FND_API.G_RET_STS_SUCCESS
THEN
IF V_REQUEST_ID IS NOT NULL
THEN SHOW CM TRX NUMBER
BEGIN
SAVEPOINT NO_DATA;
SELECT TRX.TRX_NUMBER, TRX.CUSTOMER_TRX_ID
INTO V_CM_TRX_NUM, V_CM_TRX_ID
FROM RA_CM_REQUESTS R, RA_CUSTOMER_TRX_ALL TRX
WHERE R.REQUEST_ID = V_REQUEST_ID
AND R.CM_CUSTOMER_TRX_ID = TRX.CUSTOMER_TRX_ID
AND R.CUSTOMER_TRX_ID = C_TRX_ROW.CUSTOMER_TRX_ID;
FND_FILE.PUT_LINE (FND_FILE.OUTPUT, V_RETURN_STATUS|| ' - AR invoice: '
|| C_TRX_ROW.TRX_NUMBER
|| ' | Generated Credit Transaction Number: '
|| V_CM_TRX_NUM||' | Success: '||V_MSG_DATA);
DBMS_OUTPUT.PUT_LINE ( 'AR invoice: '
|| C_TRX_ROW.TRX_NUMBER
|| ' | Generated Credit Transaction Number: '
|| V_CM_TRX_NUM||' | Success: '||V_MSG_DATA);
---REMARKED THE AR INVOICE WAS GENERATED CM--
UPDATE RA_CUSTOMER_TRX_ALL TRX
SET TRX.ATTRIBUTE7 = 'Y',
TRX.ATTRIBUTE8 = V_CM_TRX_ID,
TRX.ATTRIBUTE9 = V_CM_TRX_NUM,
TRX.ATTRIBUTE10 = V_REQUEST_ID,
TRX.INTERFACE_HEADER_ATTRIBUTE12 = NULL
WHERE 1 = 1
AND TRX.ORG_ID = P_ORG_ID
AND TRX.CUSTOMER_TRX_ID = C_TRX_ROW.CUSTOMER_TRX_ID;
UPDATE RA_CUSTOMER_TRX_ALL TRX
SET TRX.TRX_DATE = V_TRX_DATE
WHERE 1 = 1
AND TRX.ORG_ID = P_ORG_ID
AND TRX.CUSTOMER_TRX_ID = V_CM_TRX_ID;
UPDATE RA_CUSTOMER_TRX_LINES_ALL RCTL2
SET RCTL2.INTERFACE_LINE_ATTRIBUTE12 = NULL
WHERE RCTL2.CUSTOMER_TRX_ID = C_TRX_ROW.CUSTOMER_TRX_ID
AND RCTL2.ORG_ID = P_ORG_ID
AND RCTL2.LINE_TYPE = 'LINE'
AND RCTL2.INTERFACE_LINE_ATTRIBUTE12 IS NOT NULL;
COMMIT;
EXCEPTION WHEN NO_DATA_FOUND
THEN
FND_FILE.PUT_LINE (FND_FILE.OUTPUT, 'AR invoice: '
|| C_TRX_ROW.TRX_NUMBER
|| ' | Generated Credit Transaction Number not found. '
DBMS_OUTPUT.PUT_LINE ( 'AR invoice: '
|| C_TRX_ROW.TRX_NUMBER
|| ' | Generated Credit Transaction Number not found. '
ROLLBACK TO NO_DATA;
---REMARKED THE AR INVOICE WAS GENERATED CM--
END;
END IF;
END IF;
IF V_RETURN_STATUS = FND_API.G_RET_STS_UNEXP_ERROR
OR V_RETURN_STATUS = FND_API.G_RET_STS_ERROR
THEN
FND_FILE.PUT_LINE (FND_FILE.OUTPUT,'Invoice Number: '||C_TRX_ROW.TRX_NUMBER||
' | Error:' || V_MSG_DATA );
DBMS_OUTPUT.PUT_LINE ('Error:' || V_MSG_DATA
||' | For Invoice Number: '||C_TRX_ROW.TRX_NUMBER);
END IF;
IF V_MSG_COUNT > 1
THEN
V_MSG_COUNT := 0;
LOOP
V_MSG_DATA :=
FND_MSG_PUB.GET (FND_MSG_PUB.G_NEXT, FND_API.G_FALSE);
IF V_MSG_DATA IS NULL
THEN
EXIT;
END IF;
FND_FILE.PUT_LINE (FND_FILE.OUTPUT, 'msg_data:' || V_MSG_DATA);
DBMS_OUTPUT.PUT_LINE ( 'msg_data:' || V_MSG_DATA);
END LOOP;
END IF;
EXCEPTION
WHEN OTHERS
THEN
FND_MESSAGE.RETRIEVE (V_DUMMY);
FND_FILE.PUT_LINE (FND_FILE.OUTPUT,
'Error in Create Credit Transaction:'
|| SUBSTR (SQLERRM, 1, 80)||' -- '||V_DUMMY
DBMS_OUTPUT.PUT_LINE('Error in Create Credit Transaction:'
|| SUBSTR (SQLERRM, 1, 80)||' -- '||V_DUMMY
END;
END IF;
END LOOP;
END CREATE_CM;
END DMAPAR03_PVT;
/

Credit Memos not seen in the Report

Hi all
My customer has a custom report which shows all the SD billed orders. The selection screens are Sales Doc# DocType, Industry Code, Material, Sold-to-party, Plant, Sales Order etc etc (all non Mandatory fields)
My problem is, any credit memos created with Order Type CR does not show up in the report. Can some one please tell me where this is controlled and how it can be made active?

Dear Madhu,
Get your custom report checked by your technical buddy (ABAP), if coding has been done to fetch data on CR order type.(Credit Memo request).
Also, if your Credit Memo billing Type is there in the output logic or not.
At the same time, get it checked from the User if this issue was there existing before or not.
Regards,
Vivek Sahni

Sale Order Credit Block due to open credit memo

Dear All,
System is blocking sale order for open items(credit). And the only open item is credit memo.
Can we avoid credit note to be considered as open item?
Thanks
Arun

Dear Arun,
Do not think this is possible in standard.
I would suggest the following way.
Currently system is giving a message during sales order creation . right?
Ask your abaper to find an EXIT before that point.
There write a code to exclude CREDIT MEMO document types from BSEG of the customer code.
It is possible as i have worked in similar requirement.
Check and revert back.
Thanks & Regards,
Hegal K Charles

Credit note from a credit memo with reference - Pricing

Hi Gurus,
I have created a Credit Memo (CR) with reference to an invoice (F2). The pricing procedure in the F2 is copied to CR, following the copy control defined. (what I expected).
However, when creating the credit note (G2), the pricing procedure selected is the one defined for credit notes, and not the one in the credit memo. (I didn't expect this).
I have this config. in the system:
- XD03: Cust.Pricing Proced: "1"
- VOV8: Docum.Pricing Proced: "P"
- OVKK: for the combination of Sales ORgDCH"P"+"1" --> pricing procedure is ZPROAC (this is pricing procedure for G2.
The pricing procedure in the Credit Memo (CR) is ZNETO1.
Copy control config is the following:
- VTFA: G2 - CR.
Copy requirements at header level: 001
At item cat. (G2N): copy requirement: 002 Item/order-related; Data VBRK/VBRP: 002 Ord-rel.credit memo
Pricing type: G
Could you provide any comments here?
Thanks
Julian

Dear Julian,
First of all Copy control does not controls the copying of pricing procedure from one doc to another.
Pricing procedure will be same as per your pricing procedure determination.
It controls the copying of values for particular condition types from one doc to another.
I have created a Credit Memo (CR) with reference to an invoice (F2). The pricing procedure in the F2 is copied to CR, following the copy control defined. (what I expected).
In this case I think Pricing procedure defined for both doc types F2 and CR is same, thats why all the pricing is copied as it is to CR.
if they are not same but all the condition types which are there in pricing poc. of F2 are also in pricing proc. of CR then pricing values will be copied without any change. (Still sequence of condition types in pricing proc. can make diff.)
pricing procedure is ZPROAC (this is pricing procedure for G2.
The pricing procedure in the Credit Memo (CR) is ZNETO1
Since the pricing procedure is different for both doc types, There could be some condition type which are there in ZNETO1 but not in ZPROAC.
Which ever condition types are common will be copied.
I will suggest you to keep pricing procedure same for both the doc types CR and G2.
Or atleast all condition types of ZNETO1 should be there in ZPROAC in appropriate sequence. (ZPROAC can have addition condition types as per your requirement.)
Regards
Mayank

In Credit Memo Net Value is coming 0.

Dear SD Expert,
I have created Credit Memo with Reference Credit memo request. While creating Credit memo (VF01) the Net Value is 0. But the Billed quantity is coming correct in the system. In Credit Memo request(VA01) every thing is ok, Quantity and Net Value are correct. But in credit memo net value is not coming as per credit memo request. I have also maintained Copy control(VTAF) for this. In copy control I have maintained following fields.
Billing document to Sales document
Choose sales document type [G2] and Billing document type [F2]
Go to Header details
[52] = Billing document header
[052]:
This routine transfers general billing header data from the reference document to target document.
[103]:
This routine transfers business data Ex: Inco-terms from preceding document to new document.
[003]
= Billing header partner:
This routine copies Bill u2013 to u2013 party form invoice to sales document.
Copying requirements [021]:
(Billing header)
This routine checks Sold u2013 to u2013 party, sales area, and currency is same or not when copying billing document to
sales document.
Item level
= TAN
153 = Item from billing document:
This routine copies all relevant data from preceding document to new
document at item category level (invoice to invoice cancellation).
104 = Business data item billing:
This routine copies business data from invoice to sales document.
Ex:
Inco-terms at item level.
004 = Billing item partner:
This routine copies Bill u2013 to u2013 party or payer from invoice to sales document.
Copying requirements [303]
= Always an item
All standard items are copied into target document
[] Uncheck copy schedule lines
[X] Update
Pricing type [D] = Copy pricing elements unchanged
As per given information kindly guide me where I was wrong and what Input is requires?
Regards,

Hello Mancy,
Indeed Naveen is correct to use Transaction VTFA. Sample Standard Settings:
HEADER:
Target Billing Type = G2, From Sales Doc Type CR
Copying requirements = 001:Header/order/related (can be customized of course)
Hint: You may COPY item number from reference
ITEM:
Target Billing Type = G2, From Sales Doc Type CR
Item Category Proposal <--THIS IS OPTIONAL (i suggest to leave this blank and input something only if you have a special business requirement wherein you need to change the item category in your credit memo, you may check Help/F1 for sample scenarios)
Item Category = G2N <--this is the item category coming from your source document i.e. item cat. from your Sales Order
Copying Requirements = 002: Item/order-related
Data Transfer Routine = 002: Ord-rel.credit memo
Pricing Type = D: Copy pricing elements unchanged
Please let me know if this helps you.
Kind regards,
Eva

FB10 - Default payment term for Credit memo

Hi,
I have question regarding the Payment terms in FB10- Credit memo entry (KG).
You must be aware that when we use F-43 or FB60 for posting Vendor Invoices (Document type KR), the payment terms on the screen will be "*", which means it should be picked up from the Master data. Similarly for posting Vendor Credit Memos (Doc type KG) using F-41 or FB65, the payment terms field is blank, which means 'Immediate payment'.
In case of FB10, Fast entry transaction code for both Vendor Invoice and Vendor Credit memo, the Payment terms for KR document is *. But for doc type KG (Credit memo), payment terms field is not blank. Instead, it is shown as *. Why is it? How can we make this blank for KG document postings. Please advise. Kindly revert in case you have any questions.
Regards,
Vinod

HI,
Please check the note 17410 for explanation.
Regards
Ravinagh Boni

Credit memo for returns

Hi experts,
If I want to create credit memo only after return delivery has been PGR, is it proper to make credit memo create with reference to return delivery? You know, SAP standard is to create this kind of credit memo with reference to return order.
If not proper, is it the reason that credit memo is set in SAP to create with reference to order or billing?
Pls advise. Many thanks.
Edited by: Cathy on Oct 17, 2009 5:13 AM
Edited by: Cathy on Oct 17, 2009 5:14 AM
Edited by: Cathy on Oct 17, 2009 5:15 AM

Hi
In standard SAP credit memo billing RE is created with reference to credit memo order type RE not with reference to return delivery and PGR
The basic reason is return order item category REN is billing relence is Order releted billing hence it doesnot refer to return delivery
In VOV7 if you make the billing relevance as A that is delivery related billing for REN then system will allow you to create credit memo with reference to return delivery only
This is the first customization reqd
Secondly there should be copy controls in VTFL between delivery type LR to billing type RE at header level and at item level for item category REN defined properly
This may not be there in standard settings and this we should define
Normally VTFA is referred for order releted billing and we are making that as delivery related so we should define copy controls in VTFL
is it proper to make credit memo create with reference to return delivery?
This is purely a client call
In one my assignments the major requirement was to create returns credit memo with reference to delivery (returned delivery qty ) only
His business prctise was
his customers will telephonically give the return order for 5 units and send back only 4 units to him
In this case if he makes a return return order for 5 and make a returm credit memo for 5 then that is not proper
So we made this customization to him for creating return credit memo with with reference to return delivery
His customers will telephonically give the return order for 5 units and send back only 4 units to him That was his operational shortcomings but we had to set the system accordingly
We used to close the balance 1 unit with reason of rejection
So according to me it is more proper to create return credit memo with reference to return delivery
Regards
Raja

CREDIT MEMO OUTPUT TYPE !

Similar Messages

Maybe you are looking for