Basic Idoc type used for Credit memo processing

Hi ,
I am working to automate the processing of Credit Memos ,Subsequent debits and credits .Can any body suggest me for the Idoc type used for posting of credit memos, which will do the same function of transaction 'MIRO' .Please help me for the above .
Please send the reply on [email protected]
Regards ,
Shilpa

Hi,
You can use invoic message type with invoic01/invoic02 type of IDoc whichever is suitable for your requirement.
Thanks.
Mark points if helpful.

Similar Messages

Which IDoc Type and Message Type to use for Credit Memo?

Could you guys please tell me which IDoc type and Message Type to use for Credit Memo? Also if possible tell me the process code/ function module.
Will certainly give points for right answer. Thank you for reading.

Hi,
You can use IDoc type FIDCCP02 with message type FIDCC1/FIDCC2 for Credit Memo.
Also you can use this FM FI_IDOC_CREATE_FIDCC1/
FI_IDOC_CREATE_FIDCC2 to generate the IDoc.
Regards,
Ferry Lianto

Idoc type used for an output type

Hi experts,
How do I find the Idoc structure used by an output type.
When i look in nace it only shows the program name as RSNASTED and form routine as EDI_PROCESSING.
Thanks,
Raghu.

I guess i have to explain the whole problem.
We are trying to eliminate a couple of items from going down to 4 output types of which 3 of them are using EDI.
So I think we should eliminate them from being populated in the line items of each IDOC.
i.e) each basic type/ extension whichever it uses.
Does it make sense?
if not please advice, I am new to EDI.
Thanks and regards,
Raghu

Change IDoc type used for XIF adapter

Hi,
I am using IDOC ZCRMXIF_PARTNER_SAVE_M01 to send data from XI to CRM. It is a generated IDOC from transaction BDFG for XIF adapter. I need to change a segment max value from 1 to 5 in order to send multiple segments. Can you please advise that from where this structure can be change so I can generate the IDoc again. Any suggestions would be appreciated.
Thanks in advance !
Regards,
Faiq

Hi Amit,
I tried that but as the IDoc is generated from BDFG so it cannot be changed from here. BDFG gives:
message type, Idoc type, Function module, Function group. Later generates the IDoc from them. I am not sure that in which of the above steps it lets me change. Do I have to make change in the function module.
Thanks in advance.
Regards,
Faiq

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.

How to Create IDOCs for a Custom Basic IDOC Type

Hi friends,
I Have a Custom Basic IDOC Type.
For that IDOC Type i need to Create an IDOC for every Header Item.
The Header Item may have variation (Different) number of Line Items.
in this case can i Use
MASTER_IDOC_DISTRIBUTE and create the Idoc for each Header Item.
or is there any way to create the IDOCs
Thanks in Advance.
Ganesh.

Hi ,
If I am not wrong you need to pass data via fm "MASTER_IDOC_DISTRIBUTE".
So you can transfer row by row data into SDATA filed of structure type :EDID ,
by concatenating the data into one field of type sdata. and passing it into the fm.
I.e defining a internal table of type EDIDD.
Try this :
DATA : itab TYPE TABLE OF edid,
 itab1 TYPE TABLE OF edidc.
LOOP AT itab2 INTO wa_itab2.
CONCATENATE wa_itab2-t1 wa_itab2-t2 wa_itab2-t3 wa_itab2-t4 wa_itab2-t5
INTO result.
itab-sdata = result.
APPEND itab.
all function 'MASTER_IDOC_DISTRIBUTE'
 exporting
 master_idoc_control =itab1
OBJ_TYPE = ''
CHNUM = ''
 tables
 communication_idoc_control =
 master_idoc_data =itab.
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

Restructuring the basic IDoc type DELVRY03

Hi experts,
My rek is to restructure the Basic Idoc type DELVRY03 for outbound delivery.
I am using IDOC_OUTPUT_DELVRY.
Is there any exit or badi for this.
Thanks

we31:
Create your new segment.
Save and remember release (edit-set release)
we30:
Create your new idoc type. Create like extension.
In your linked idoc type fill your standard idoc type.
Press create new sement button for add segments and put your Z segment created in we31 with min and max quantity.
Save and release the idoc type
Regards

What is the message type and basic type used for catsdb in idoc help me

what is the message type and basic type used for catsdb in idoc help me
ANY IDOC FOR CATSDB PLEASE TELL,
Regards,
Jagrut BharatKumar Shukla
points will be awarded

Hi,
Check these message types.
ATT_ABS_WITH_COST and WORKSCHED_WITH_COST.

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

Other document type for credit memos in MIRO

Dear,
i would like to use a seperate document type for credit memos posted with MIR0 compared to RE for invoices. I created a new Z transaction. And now I thought that I could enter this new transaction code in OMR4 (tablle V_169F), but I can not add a new customised transaction in this list. What can I do?
Or is there an other way to have another document type for credit memos?
Thank you.
Leen

Hi
You can create a new document type for credit memo through t code OBA7. Once the T code is created with all necessary parameters you can assign this to MIRO transaction.
You cannot create a customised transaction through OMR4. This is meant for assigning the Doc type to Invoice verification
Regards
Jaswanth

What is the Correspondance type for Credit Memo Form?

Hi,
I need to use the Credit Memo Form for taking Printouts. Kindly tell me which is the standard Correspondance Tyep that i can use to take this Printout?
It would be a great help if any one can provide some inputs on this..
Thanks
Kishore

Use SAP11.

Basic idoc type for asset creatioon and asset acquisition

Hi
Please can anybody tell me the basic IDOC type provided by SAP for
- Asset creation
- Asset acquisition.
Thanx in advance....

Hi,
Go through this link
http://www.sap-basis-abap.com/fico/configuration-in-asset-accounting.htm
help.sap.com/bestpractices/BBLibrary/documentation/B44_BB_ConfigGuide_EN_Nordics.doc
Reward points if found helpful...
Cheers,
Chandra Sekhar.

I am receiving Basic Idoc Type error while I am executing SWO1 for BKPF

Hi
I am receiving Basic Idoc type error message while I am trying to test BKPF object. Please note that the Business Object is delegated to a custom BO. Can anyone tell me where the linkage is established between IDOC type and BO.
Thanks
Arghadip

Arghadip,
Can you check the transaction WE57?
Thanks

Condition type used for invoice list

Hello Gurus,
following condition type used for invoice list, why do they exit in invoice list:
RL00 MW15. LR00 RD01

Hi,
Please go through the below document
When you work with invoice lists, you need to be familiar with the following concepts:
Prerequisites for invoice lists
Relationship to Pricing
Structure of an Invoice List
Changing header and item data
Integration with financial accounting (FI)
Prerequisites
You can only process invoice lists if the following prerequisite data is defined by your system administrator in Customizing for Sales:
Condition type RL00 (factoring discount) must be maintained and, if required, also the condition type MW15.
An invoice list type must be assigned to each billing type that you want to process in invoice lists. The standard version of the SAP R/3 System includes two types of invoice lists: LR for invoices and debit memos, LG for credit memos.
Copying requirements must be defined (for example, the payer, terms of payment and other fields that must be identical in the documents to be included in the invoice list)
In addition, before you process an invoice list, you must maintain the following master data:
A customer calendar must be defined, specifying the time intervals or dates on which invoice lists are to be processed.
The customer calendar must be entered in the Billing Sales Area view of the customer master record.
Pricing condition records for the condition type RL00 and, if necessary, (e.g. in Germany) the condition type MW15 must be maintained.
Output condition records for condition types LR00 and RD01 must be created.
Relationship to Pricing
The system processes factoring discounts in invoice lists in exactly the same way as other kinds of pricing elements. The data for the factoring discount is stored in condition records. Controlling during document processing is carried out via condition types, pricing procedures and access sequences. This control data is defined in Customizing for Sales by your system administrator.
For further information, see Conditions and Pricing.
Structure of an Invoice List
An invoice list represents an individual billing document. It consists of a document header and document items. Each item represents a billing document that you have included in the invoice list. The header contains an overview of summary information, such as the net value of all documents in the invoice list, the value of the factoring discount, details of taxes, and so on. It also contains information on partners and output.
Changing Header and Item Data
You can change some of the header data - for example, the billing date - when you process the invoice list. You can change an item - either an individual or collective invoice - and display document details. However, you cannot change any data in individual billing documents once they are part of an invoice list.
It is possible, however, to make certain global changes to output in all items in an invoice list.
For further information on output, see Communication in Sales and Distribution Processing.
Integration With Financial Accounting (FI)
The documents that you want to combine within an invoice list must already have been billed and forwarded to Financial Accounting. Here the billing documents intended for an invoice list are blocked for normal dunning transactions.
The dunning block on FI documents is lifted as soon as you create an invoice list and transfer it to FI . The system then calculates the new dunning date for the invoice on the basis of the invoice list date.
In addition, the system enters invoice list numbers in the FI documents as reference numbers. Invoice list numbers can then be entered for incoming payments.
When you save the invoice list, the system automatically creates an accounting document for the factoring discount and possible taxes and posts it to the corresponding G/L account in FI.
Regards,
Murthy

EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

Hi All,
We are facing some issues regarding EDI 821 and EDI 823 file mappings.
We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
EDI 823 - Lock Box
Basic IDOC type - FINSTA01
Message type - FINSTA
Process Code - FINS
The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
EDI 821 -
Basic IDOC type - PEXR2002
Message type - PAYEXT OR REMADV
Process Code - PEXC OR REMA
We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
We are trying different combinations but nothing is working so far.
I need the following things to proceed furthur.
1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
2)If those are not correct, can you please let me know the correct entries
3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then I can re check it.
4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
thanks in advance for all your help.
Please let me know if my question is not clear.
Thanks,
Ramesh.

Hi Ramesh,
I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
Are you can give me the exact error and i can help you as well.
Thanks,
Mahesh.

Basic Idoc type used for Credit memo processing

Similar Messages

Maybe you are looking for