Credit memo not generated for RMA Receipt

Hi,
i created RMA receipt but for this credit memo not generated in AR, Manually i have run the Workflow Background Process & Receiving transaction processor concurrent also. even though CM not generated(In AR Interface lines table also data is not available)..or else is there any possibility for cancel or return the RMA Receipt quantity?
regards
Balaji
Edited by: user9122706 on May 15, 2012 9:22 PM
Edited by: user9122706 on May 15, 2012 9:51 PM

Dear Balaji,
Credit memo not generated for RMA Receipt,Can u put manual credit in AR
Regards,
Shineee..

Similar Messages

INTRASTAT / EXTRA - Credit memo not relevant for declaration

Hi all,
I have this problem with INTRASTAT declaration:
Transaction VE08 mark credit memo as not relevant for declaration with this description "No association to a goods movement was found".
Do you have any solutions?

Hello,
check VE80, if you have an exclusion indicator on the item category.
If not try to run VE01 for your country and mark only credit memos. Use log type B. Check the message in the incompletion log. If your credit memos are not in the incompletion log, than run the transaction transaction VE08 you run before again. The credit memos should show up, otheriwse let me know what is the message in the incompletion log.
Check also if you need to show credit memo from legal point. From my point of view it should show only data related to deliveries.
Try and reply.
Edited by: SAPSD1000 on May 25, 2009 6:03 PM

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

Excise Accounting document not generated for Imported Asset GR

Dear all,
Excise accounting document is not generated for imported asset goods receipt(MIGO)
but "C" Register part 2 no. is generated,usual accounting document is generated for GR,
Asset is Dr to GR/IR
Process is
1. Create asset purchase order with acct. assignment "A",
2. Customs miro based on p.o.
3. Do GR with excise
4. Post invoice for orginal vendor.
What will be cause of this problem ?
How to solve this issue ?

The above issue may be due to Accout assignmnet -A . Check your accout assignment in spro -mm-purchasing -accout assignment - Asset A - GR Non valuated has Ticked on . If it is ticked on - No Fi entry will happen at the Time of GR .
The reason being , if an FI entry happen for the first time , asset is capitalised . To avoid this GR is made in ur config as this .
rewdzzzz is full if correct
Edited by: manu m on Apr 24, 2010 11:11 AM

Accounting document not generating for excise invoice.

Dear all ,
my issue is
accounting document not generating for excise invoice
we are creating accounting document in J1iin
with refferance to billing document but the accounting docuemnt is not generating
the accounting document for billing document is generated
so why the accounting document for excise invoice is not genrating its showing the correct amount in BED ,cee and HE Secc.
please help
regards
Subrat

IMG -> In Logistics u2013 General -> Tax on Goods Movement -> India -> Account Determination -> Specify Excise Accounts per Excise Transaction
Check if the following is maintained or not
DLFC       CR Credit      PLAAED PLA AED account
DLFC       CR Credit      PLAAT1 PLA AT1 Account
DLFC       CR Credit      PLABED PLA BED account
DLFC       CR Credit      PLACESS PLA cess account
DLFC       CR Credit      PLAECS PLA ECS Account
DLFC       CR Credit      PLASED PLA SED account
DLFC       CR Credit      RG23AED RG 23 AED account
DLFC       CR Credit      RG23AT1 RG 23 AT1 Account
DLFC       CR Credit      RG23BED RG 23 BED account
DLFC       CR Credit      RG23ECS RG 23 ECS Account
DLFC       CR Credit      RG23SED RG 23 SED account
DLFC       DR Debit       MSUSP CENVAT suspense account
Also IMG -> In Logistics u2013 General -> Tax on Goods Movement -> India -> Account Determination -> Specify G/L Accounts per Excise Transaction
Check if for all Excise group u2013 DLFC u2013 Company Code combination GLs are maintained or not (especially in production client)

Accounting document not generating for excise invoice-please help

Dear all ,
my issue is
accounting document not generating for excise invoice
we are creating accounting document in J1iin
with refferance to billing document but the accounting docuemnt is not generating
the accounting document for billing document is generated
so why the accounting document for excise invoice is not genrating its showing the correct amount in BED ,cee and HE Secc.
please help

Dear G. Lakshmipathi,
As uknow i am getting problem when i am creating the debit memo
so is there any specific ETT for debit memo is there .because we are not maintaining delivery type to billing type here in CIN setting
so its not goods removal through sales . so what will be transaction type for this.
how to check the error that why the accounting document is not generated as no error log is also comming.
so please help me in this regards.
Thanks with Regards
Subrat

Credit memo not saving

Hi all,
I have a customer who is trying to save a couple credit memo and when she clicks on execute it highlights the quantity field and doesn't save. The credit memo is working for other invoices in the same area. The customer is using SAP B1 2005 Pl 45. Any suggestions would be appreciated. Thanks!
Jeff Haldeman
Support One

Gordon,
Believing it is AR Credit Memo we are talking about it increases the quantity on stock and not reduce..
Suda

Cancel Credit Memo Not passed to Accounting

Hi, All
My client have a Issue there raised Credit memo request with reference to billing document later there convert into Credit Memo, later there found amount there given is wrong credit memo request, there cancel credit memo the problem is that system not generate any accounting document Due to the Number range Issue and we fix the issue ( Same Series of number ranges RV and accounting ) previous it was the other Series of number ranges
The problem is Cancellation of credit memo not passed to accounting and credit memo already passed to accounting
Can we delete Billing document not passed to Accounting So i can again Cancel the Credit memo
it very urgentt
Thanks
Rajesh

Hi,
to cance a cancellation document, check note 388489.
But the status of the original document won't change thus you cannot cancel it again. The solution is creating a debit memo.
Balazs

Cancellation / Reversal of Credit memos and Check for payment

I have few cases where the credit memos and check for payment documents have been keyed with an incorrect posting date.
What should be best approach to reverse these transactions.

Hi Somchitra,
in such situations ideally you would use the cancellation document standing on the original document, alas, a credit memo has no target document.
You will need to create an invoice with exactly the same data as in the credit memo & then internally reconcile these transactions. If the credit memo was in itself generated from an invoice, you need to cancel that reconciliation first. After that you re-create the credit memo with exactly the same data, just with the correct dates.
To cancel the cheques for payment you need to cancel the payment itself with the original document date & 'Cancelled' will be put in the 'Remarks' on the cheque.
You will then need to recreate the payment with the correct dates.
If you have already confirmed the printing of the cheque, you'll need to issue a new cheque number & destroy the printed copy, if it hasn't been printed, you can select the appropriate number in the 'Cheque number confirmation' window.
As always when correcting transactions, please keep an eye on the stock transactions & make sure they are correct. Also, for auditing purposes, always enter an approriate text in the 'remarks'.
All the best,
Kerstin

Lines are not generated for holidays and sundays

Hi
creating a sale order shcedule lines are not generated for sunday for a particular plant .
Schedule lines are generated for subsequent monday only.
the plant calander is also correct
with regards
partha

Hi
I would really double check the factory calendar ans the of the plant and sales organisation
regards,
Sidi

TimeStream Error (not generated for year 1970)

Dear Experts ,
I am facing a problem with Time Stream .... When i try to open a Planning Book i am receiving the following message:
Timestream (TS ZBRSNP_ZF ) not generated for year 1970
Message no. T9507
Diagnosis
The date is outside the periods maintained in the factory or planning calendar (timestreams).
System Response
The error causes a system crash.
Procedure
a) Regenerate the timestream as far in the future (or possibly the past) as possible
or
b) Use the report ZZTSTRDELE to delete the runtime objects of the timestreams, if changes have been made to Customizing settings. For more information, see SAP Note 169885.
It starts happen after i included Initial Column at Planning Book .... The Factory Calendar that i am using starts on 2006 and ends on 2020 .... The timestream i am using is looking for 2 years in the past and 9 years in the future.
*The message above says that it is necessary to execute report ZZTSTRDELE but i am having some problems while donwloading SAP note. It is possible do delete it manually? exist another way to fix this issue?
Please i hope someone can help me as soon as possible ....
My Best Regards
Mauricio Filho

Hi Sunitha,
We have same type of problem now, could you plz adivise me how to fix this error and where we need to configure to overcome this error.
Thanks in advance
Sreeenivasu

J1INQEFILE is not generating for the month of March 2011

Hi,
J1INQEFILE is not generating for the month of March 2011, we have executed Qefile from 01/01/2011 to 31/03/2011 then file is generating but March 2011 data is not available.
Problem is challans were updated in the month of April 2011 for March 2011 documents, When we executed J1INMIS report with Bank Challan status, documents are coming in the report.
As per our understanding Challan numbers and Bank Challan update should be done in the month of March 2011 but challans and Bank challans were updated in the April 2011.
Please suggest.
Thanks,
Ratnam

Hi Vara,
Please check following thing in the system.
1) When the Challan is created ( March month or April 2011)
2) When the Bank challn updated for the challans
3) If the Challan created in the April and generating returns for the month of March 2011.
4) Check in J1INMIS report for the month posting date 01.03.2011 to 31.03.2011, if the external Challan number is appearing or not for the documents.
5) If the Challan created in the April ask user to revere through J1INREV, and make Challan in the month of march 2011.
Problem will solve.
Thanks,
Ratnam.

SD Credit memo note process

Hi Gurus,
My concern is " My user was creating Credit memo note on certain order reasons, and based on this order he will be doing billing, now he want that system has to trigger separate G/L accounts based on order reasons. Can it be done in standard SAP system.
Please consider this issue as top priority.
Thanks and regards
SUBBU

You can give order reason in VKOA, but first you shall have to create a cond table with the appropriate fields (like Order reason)
it is same as giving Acc Key (ERL etc.) in VKOA, but first you have to create a cond table with field Account key.
It is all part of standard configuration.
Order reason is a field already provided (technical name mentioned by member). You have to complete the configuration steps, which shall lead to amount being posted to right account, after system finds a valid condition record.
Thus check if there is a cond table already with the fields you want.
Check if this cond table is in your access seq.
Then create condition record in VKOA
Test by creating and posting a credit memo.
Edited by: Typewriter on Sep 27, 2011 1:40 PM

Connection has no password, -jdbc.xml file not generated for connection

Hi,
I'm migrating a jdev 10g web application (with EJB) to 11g, i did the automatic migration tool offred by 11g, i'm using the integrated weblogic server but it seems there is a *-jdbc.xml file missed, and it must be generated, this is the log file of the start of server :
IntegratedWebLogicServer started.
[Running application SAB_ADMIN on Server Instance IntegratedWebLogicServer...]
[09:14:15 AM] ---- Deployment started. ----
[09:14:15 AM] Target platform is (Weblogic 10.3).
[09:14:18 AM] Retrieving existing application information
[09:14:19 AM] Running dependency analysis...
[09:14:19 AM] Deploying 4 profiles...
[09:14:21 AM] Wrote Web Application Module to C:\Users\Moshe\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\SAB_ADMIN\ViewControllerWebApp.war
[09:14:21 AM] Wrote Web Application Module to C:\Users\Moshe\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\SAB_ADMIN\ModelWebApp.war
[09:14:25 AM] Wrote EJB Module to C:\Users\Moshe\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\SAB_ADMIN\ModelEJB.jar
[09:14:25 AM] WARNING: Connection DBConnectionSAB has no password. DBConnectionSAB-jdbc.xml file not generated for connection DBConnectionSAB.
[09:14:26 AM] Wrote Enterprise Application Module to C:\Users\Moshe\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\SAB_ADMIN
[09:14:26 AM] Deploying Application...
<14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:28.065--ServerSession(40464643)--property eclipselink.jdbc.user is deprecated, property javax.persistence.jdbc.user should be used instead.>
<14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:28.299--ServerSession(40464643)--property eclipselink.jdbc.driver is deprecated, property javax.persistence.jdbc.driver should be used instead.>
<14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:28.299--ServerSession(40464643)--property eclipselink.jdbc.url is deprecated, property javax.persistence.jdbc.url should be used instead.>
<14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:28.299--ServerSession(40464643)--property eclipselink.jdbc.password is deprecated, property javax.persistence.jdbc.password should be used instead.>
<14 oct. 2010 09 h 14 GMT+01:00> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.lang.Object oracle.user.Session_user.mergeEntity(java.lang.Object)' in EJB 'SessionEJB' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'SessionEJB' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<14 oct. 2010 09 h 14 GMT+01:00> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.lang.Object oracle.user.Session_user.persistEntity(java.lang.Object)' in EJB 'SessionEJB' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'SessionEJB' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<14 oct. 2010 09 h 14 GMT+01:00> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.lang.Object oracle.bouton.Session_bouton.mergeEntity(java.lang.Object)' in EJB 'Session_bouton' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Session_bouton' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<14 oct. 2010 09 h 14 GMT+01:00> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.lang.Object oracle.bouton.Session_bouton.persistEntity(java.lang.Object)' in EJB 'Session_bouton' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Session_bouton' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<14 oct. 2010 09 h 14 GMT+01:00> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.lang.Object oracle.operation.Session_operation.mergeEntity(java.lang.Object)' in EJB 'Session_operation' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Session_operation' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<14 oct. 2010 09 h 14 GMT+01:00> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.lang.Object oracle.operation.Session_operation.persistEntity(java.lang.Object)' in EJB 'Session_operation' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Session_operation' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:29.656--ServerSession(42285779)--property eclipselink.jdbc.user is deprecated, property javax.persistence.jdbc.user should be used instead.>
<14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:29.656--ServerSession(42285779)--property eclipselink.jdbc.driver is deprecated, property javax.persistence.jdbc.driver should be used instead.>
<14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:29.656--ServerSession(42285779)--property eclipselink.jdbc.url is deprecated, property javax.persistence.jdbc.url should be used instead.>
<14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:29.656--ServerSession(42285779)--property eclipselink.jdbc.password is deprecated, property javax.persistence.jdbc.password should be used instead.>
<14 oct. 2010 09 h 14 GMT+01:00> <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application C:\Users\Moshe\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\SAB_ADMIN\ModelWebApp.war. Please make sure that the annotations are valid. The error is oracle.adf.view.faces.webapp.ResourceServlet>
<14 oct. 2010 09 h 14 GMT+01:00> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1287044066833' for task '0'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'SAB_CRUD-Model-context-root''
weblogic.application.ModuleException: Failed to load webapp: 'SAB_CRUD-Model-context-root'
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:404)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.adf.view.faces.webapp.ResourceServlet
     at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
     at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
     at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
     Truncated. see log file for complete stacktrace

This is the content of my web.xml file where i found the markup <servlet> and i tried to run without the first one but the error still like it was :
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>resources</servlet-name>
<servlet-class>oracle.adf.view.faces.webapp.ResourceServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>resources</servlet-name>
<servlet-class>org.apache.myfaces.trinidad.webapp.ResourceServlet</servlet-class>
</servlet>
<servlet>
<description>Web Service MyConnexionServiceSoapHttpPort</description>
<display-name>Web Service MyConnexionServiceSoapHttpPort</display-name>
<servlet-name>MyConnexionServiceSoapHttpPort</servlet-name>
<servlet-class>oracle.controll.ConnexionBaseDeDonnees</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>ResultatRequetePort</servlet-name>
<servlet-class>oracle.controll.ResultatRequete</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>resources</servlet-name>
<url-pattern>/adf/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>MyConnexionServiceSoapHttpPort</servlet-name>
<url-pattern>MyConnexionServiceSoapHttpPort</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ResultatRequetePort</servlet-name>
<url-pattern>/ResultatRequetePort</url-pattern>
</servlet-mapping>
Thanks...

List of credit memo note

Hi There,
How can we list all the credit memo note (billing document).
Cheers.

Hi chan,
go to vf05n there you give billing document type i.e G2 give dates
you will get list of documents
i think it should give solution to your problem
cheers
bvdv

Credit memo not generated for RMA Receipt

Similar Messages

Maybe you are looking for