Error when releasing credit memo to accounting

Hi,
When I try to release the credit memo to accounting the system throws the following error "Account type/account for invoice reference does not match item".
Anyone know the reason please?
Thanks,
Shankar

Dear Shankar,
This error occurs the following reasons.
1. Revenue account determination has not been properly set.
2.check in VOFA where under General control, document type is there, you need to mentioned RZ(Billing doc.transfer) and also check accoun determination procedure in billing documnet as well as credit memo.
3. copying control.
Plz check and revert.
Regards,
Narasimha

Similar Messages

Error when posting credit memo in current year

Hi all,
When I am trying to do credit posting to an asset in current year it is giving me follwing error. Can someone help me what can be done.
Balance for transaction type group 10 negative for the area 01
Message no. AA629
Asset affected: 000170009993-0000
Diagnosis
With the transaction entered, the balance for the transactions in group 10 in area 01 will be negative in this fiscal year. However, the balance of transaction type group 10, according to its definition, must be positive in each fiscal year.
System Response
The system rejects this posting.
Procedure
Check the transaction type, the amount and the fiscal year in your posting. If you want to post a credit memo to an acquisition from the previous year, then use a transaction type for a retirement. If necessary, you can change balance rules after talking with your SAP consultant.
Thanks,
Sarada

Hi,
i think you've chosen the incorrect tansaction type ( perhaps 100) for your credit note . try to post your CN with another transaction type; e.g. 160 or 161, which do not belong to transaction type group 10.
you can check this with trx. OA81
regards Andreas
pls reward useful answers
thank you!

Currency Type error when releasing billing docs to Accounting

When I am trying to release the billing documents to accounting following error is displayed :
company code ABC has currency type 31. the currency type has the currency key INR in the Fin. Accounting application. The same currency type is conveyed to fin. accounting accross the accounting interface with currency key CAD.
System is also showing the tip :
This is a system error in the calling application. Currency type 31 in company code ABC must have currency key 'CAD' when the data is transmitted.
Please let me know if I have to do anything in Tcodes SCC4 or OB22. Detailed answer will be of help.
Regards
RK

Hi Ravi,
From the discription of the error what you have given what i umderstood is that in FI documents are posted with Currency INR, while the Cur. type 31 is transferring Cur. Key CAD to FI.
Since there is a diff in the Cur the error is coming.
Try to maintain Add. local cur in OB22 and then check.
regards
JS

Error when releasing billing to Accounting

Hi All,
I get the following error when releasing the billing to accounting in T-code VFX3....
Tax code in procedure TAXSL is invalid
Message no. FICORE704
Diagnosis
The tax code entered is not defined in the country for this company code.
System Response
Procedure
Check and, if necessary, correct the entry.
Procedure for System Administration
If it is not an input error, check and possibly change the system settings.
To do this, choose Maintain entries (F5).
1. Check whether the required tax determination procedure is assigned to the relevant country. the Procedure field is in the detail screen.
2. Create a new tax code if required
Pls note that in the error message it does not mention a particular tax code which is invalid, it jus shows tax code in procedure TAXSL is invalid.
I have done the following customization both in FI and SD.
I have maintained condition record MWST both in FI and SD. Maintained all necessary tax codes in FTXP.
Note that in the billing, we enter the condition type MWST in the Header Level and enter the relevant percentage manually. According to my understanding since the condition is maintained at header level there is no need of maintaining condition records through T-Code VK11.Therefore the tax code is not picked from the condition record as its not maintained in the item level.
Pls advice me on how to overcome this error ASAP since its critical.
Thanks in Advance,
Maleeq

Hi,
Yes I have maintained tax codes in FTXP. but the error message shows that "tax code __ is missing in tax procedure TAXSL". To my knowledge it is not possible to create a tax code "blank"!!!!
I have not maintained condition records in VK11 as we maintain the MWST condition in the Header level. Condition records are picked only from ITEM level and NOT from HEADER level.
Maleeq

Create IDOC when the credit memo is generated

I want to create an IDOC.
The IDOC will be created when the credit memo is generated.
Please help me to create the segments.
Title was edited by:
Alvaro Tejada Galindo

Hi
First you find the relative Idoc Type and Message type for that credit memo in the tables EDBAS and EDMSG
Then go to WE31 and create the additional segments as per your requirements apart from doing lot of other related settings
see the doc
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Regards
Anji

Getting Msg: Error when calling Credit Management: Technical Error

Hi All,
While creation of sales order in ECC, i am getting a message "Error when calling Credit Management: Technical Error"
Can you help me in this case
Regards,
Satish

Satish,
Just so you know, this BADI "links" SD module to FSCM credit management. If you use the right code in this BADI, it copies over credit information on to the sales order such as Credit Account, Risk Class and Credit representative code. (Later this risk class, order's credit control area and credit group is used to look up the appropriate line in OVA8 settings)
Now you could be getting this error for any of the issues:
1. If the business partner is not created for the customer for which you're trying create a sales order (The credit account (sales order header) should have a relevant BP already) Check if the BP is correctly created.
2. Next if the credit data has been maintained for the BP in credit management.
3. XI/PI connectivity issues etc
Check if all this is maintained and you should be good. Cheers

Error while releasing credit block for the order

Hi all,
I am getting follwing error while releasing credit block for the order in VKM1
Incorrect index structure for table IVBEP1
Text
Incorrect index structure for table IVBEP1
Diagnosis
Internal error.
Procedure
Repeat the transaction.
If the error occurs and you have a CRM System connected to your SAP R/3 System, the document may have been archived in the CRM System.
If the error occurs again, inform your system administrator. If the error cannot be corrected, call the SAP Hotline directly. Describe which steps preceeded the error.
But we are not transfering any orders to CRM.The order can be only seen in R/3
Please assist
Regards
Mano

Hi
KIndly check the oss note 505876 in may help you
Regards
Damu

Error when releasing a transport

Hello experts,
I am getting an error when releasing a transport. The error message is telling me that
Object DTPA DTP_009C8T81IIB6H4UFC7FQUVRFL was set to 'inactive'
The detailed error message isnt very helpful. The performance assistant gives the error message RSO 407.
I found another thread, scn.sap.com/thread/3428031
The answer in this thread appears to be very close to a solution for me, I just need a little more information I think. As it says, I have looked in the table RSTRAN for the transformation that this DTP processes. There are three rows, with a different OBJVERS. A and M are both set to ACT, but OBJVERS = D is set to OBJSTAT = INA.
I suspect that this is the problem with the releasing of my transport. Do you agree?
If so, how do I go about getting this activated?
Many thanks.

Hi Simon,
The D version will be always inactive as it indicate SAP Delivered version of the transformation.
I will suggest just have a look at any existing transformation, you will find same status i.e D version INA also check last change it will be SAP also under content column you will find info for D version.
I still say, just go ahead and release your transport by ignoring the message, it should work. You are all set to move your transport.
Rest upto you.
I have tried releasing transport by ignoring messages many times.....and worked all time
Thank-You.
Regards,
VB

Error while releasing an invoice for accounting.

Hi Experts,
I am encountering an error while releasing an invoice for accounting. The error displayed is 'error in transaction currency'. Please help me out with this.
Regards,
Sunita

Hi Rish,
Simply go to FS00 and click on edit cost element and for CElm Category give some input based on the G/L account type.
You might have to seek help of an FI consultant to do so.
Also in KA01 create this G/L account as a cost element against your controlling area assigned to your Chart of Accounts, you can do so by clicking on Extra's tab in transaction KA01.
Just let me know if it works.
Reward if helpful.
Regards
Ravi

How to create an idoc when the credit memo is generated!

My requirement is "An idoc will be generated when the credit memo is created "
What is the possible way to that.
Please send me steps (with screen shots if possible)
thnks

Re: How to create a credit memo !
Reward point..

Error in creating Credit Memo

Hi,
AI is returning the below error for a credit memo
The document created must have a non-positive total amount because the creation sign for your transaction type is Negative.
The amount on the line is already having a negative value.
Can you please advise what could be the issue?
Regds,
Jaya

Hi Octavio,
There is only 1 line for this CM with line type ='LINE'
We just saw that previous_customer_trx_id was null for this null. On populating this value manually, the credit memo was generated.
Not sure why this value was null initially.
Regds,
Jaya

IS-H Error when entening a new bank account in Patient Admission

Hello,
We have the following IS-H Error when entering a new bank account in PatientAdmission
Bank control key and bank key do not match.
Message number: AR142
We do not have this problem when entering this bank account in Change Customer.
Thanks in advance
Best Regards

Database Vendor Code: 1005 is being passed from the database client through the report engine - unmodified. E.g.; look for the error in your database documentation.
See:
Failed to retrieve data from the database. Details: [Database Vendor Code: &lt;vendor code number&gt;].
Failed to open the connection. Details: [Database Vendor Code: &lt;vendor code number&gt;].
Compare the version of the client you are using and "other people" are using.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter

Unexpected error when re-enabling an AD account

Hi,
I am receiving an "unexpected-error" when exporting a previously disabled account to AD as a re-enabled account.
Here's the scenario:
User is returned to the delta view, which should move them back to the Active Accounts OU (from the Inactive Accounts OU).
The export does move the user to the Acitve Accounts OU, however, the user is disabled, and the export reports "unexpected-error".
A subsequent sync will change the user to enabled without any errors.
The event viewer reports this error, that baffles me a bit:
"BAIL: MMS(1848): tower.cpp(3855): 0x80004005 (Unspecified error)
BAIL: MMS(1848): csobj.cpp(2112): 0x80004005 (Unspecified error)
BAIL: MMS(1848): expcall.cpp(864): 0x80004005 (Unspecified error)
ERR: MMS(1848): expbase.cpp(2902): PutAnchorWithDnInternal failed on CS object {CB0DE8C8-15F4-48CC-8A67-3214E4D3DE85} with 0x80004005 (pass 1 of 5)
Forefront Identity Manager 4.0.3576.2"
All my searches say a hotfix addressed this in ILM, but I'm unsure if that would be an appropriate approach for FIM.
Any ideas or suggestions are appreciated.
Thank you for any help.
Sami

Thanks Ed,
Phew, sorry to hear your case was not solved …
On the other hand, this is yet another indication and confirmation of where the issue seems to be. I was told pretty much the same by Microsoft Support. I can actually confirm, based on my tests,
that the change must have occurred between FIM and FIM R2. Code extensions originally written for MIIS worked just fine in FIM but break in FIM R2.
How come Microsoft did not anticipate that their change will break existing logic? I would have expected some kind of advanced notification/warning in the FIM R2 documents …
My problem is that we need to move on.
In absence of any solution from Microsoft after so many months, I’m reviewing our business logic to code around this new restriction; essentially I’m trying to remove the blocks of code
that would lead to such a scenario.
I’ll post an update if I hear of any resolution from Microsoft.
Radu Popa

Pricing error while making Credit Memo

Dear Gurus,
While making credit memo with reference to credit Memo request i am getting pricing error on the basic price.
Please note i am getting this error only while making credit memo under this conditions
1. while using Invoice as reference while making credit memo request and than making credit memo with reference to credit memo request.
Please note i am not getting this error while the credit memo request is not refrenced to Invoice.
I am using the same document types for both the scenarios. I have checked copy control and the Pricing type maintained is "D".
Please let me know what could be the possible error.
Thanks for your help in advance.
Regards
Shrads

Hi,
Please check your credit memo document type for document pricing procedure in VOV8.

Error when releasing billing to accounting document

Why we tried to release the billing to accounting document. There is the below error.
Could someone please kindly help?
Message Identification: F5
System Message Number: 358
Output type: E
The Diagnosis is 'This document refers to a document which contains an invoice reference.
The Procedure is 'Enter a different document as the invoice reference'.
Thanks,

You might be creating the billing document for a flow where there might be original invoice and/or credit memo also.
So check that the original invoice and/or credit memo has an invoice reference to itself (i.e. the invoice reference = the accounting document number) than there is an incorrect referencing.
Remove this reference via FB02 in the original invoice and/or credit memo and it should work
Regards,
Gaurav

Error when releasing credit memo to accounting

Similar Messages

Maybe you are looking for