Error while creating J1IJ w.r.t Delivery document

Dear All,
I am getting an error while creating an outgoing excise invoice for a Depot Transaction.I have an OBD with one line item and the PGI has been done for the same .While going into the J1IJ screen w.r.t to the delivery no .Here for the same OBD i am getting 2 line items i.e one with a zero qty and the other with actual delivery qty .I couldnt figure out this error can anyone help me on this error.
Regards,
Vivek.k

Verify the determination of Storage Location & Warehouse and also
Refer SAP Notes
833748 & 497287

Similar Messages

Error while creating a transfer order for delivery note.

Hi Gurus,
I have already created an outbound delivery. I am creating a transfer request as a basis for goods movement in the warehouse and to print the picking list. so i use the path:
Logistics -> Sales and Distribution -> Shipping and Transportation -> Picking -> Create Transfer Order -> Single Document.
Now here i enter the warehouse number, plant, delivery. when i press enter i get error "No items that are to be picked were found".
I went to the following IMG path -- Enterprise Structure --> Assignment --> Logistics-Execution --> Assign Warehouse number to plant/storage location.
Assign the warehouse to the plan and storage location.
Still i get the same error. Could some one help me out here?
Thanks in advance
Amit

Hi,
can you check whether Warehouse number exists and transfer order creation is required or not at Delivery document under Picking tab

Error while creating excise invoice to return Delivery (J1IS)

Dear all,
Plz help to solve this problem.
After MIGO. I have done return delivery to vendor(Movt-122).
With ref to the return delivery doc I am trying to create excise invoice to send to vendor in J1IS.
but error appears as Vendor not related to material documents.
Thanks & Regards
Sanjay Larokar

Hi Sanjay,
Apply Below Notes
1042131     Vendor displayed as incorrect in J1IS if no leading zeros
1025204     Vendor not recognized in J1IS and error 076 displayed
1008100     Error "Vendor not related to Material doc" displayed in J1IS
1003491     Vendor not recognized in J1IS and error 076 displayed
960564     Vendor code truncated in J1IS resulting in Error 8I 786
Cheers...
Santosh

Error while creating inbound delivery

Hi All,
I get an error while creating inbound delivery from ASN
"Error during conversion of unit of measure: UoM is missing -> ST BOR131
Please help solve this issue.
Thanks in advance
Regards,
Thiru

hi,
please maintain the uom for tour material.
or
reffer this link
Alternate Unit of Measure Conversion Rule Error
/thread/2000551 [original link is broken]
Thanking you.

Error while creating delivery for STPO

Dear ALL,
I am facing the following error while creating delivery based on the purchase order.
""""Essential transfer parameters are missing in record""""
Pls help me how can I proceed further.
RGds
Babu

Hi
What is the document type for the purchase order ? It seems that we may take wrong PO number in delivery creation

Error While Creating Delivery : "Quantity falls below minimum Inventory"

Hi All,
I have an error while creating a delivery in BusinessOne. I have created a new item using the BusinessOne UI. And i created the salesOrder for this item and it was created successfully. But when i tried to create a salesDelivery for this Item i am facing an error that "Quantity Falls below Minimum Inventory".
How can i solve this? How can i add quantities for this item in the inventory?
Thanks in Advance,
RAMU.

Hi Ramu,
also you can make sure you are choosing the right WH in ctrlshiftS windows if You do, then chek on Inventory -> Inventory report -> inventory status if you have enought and available quantities for the delivery, if you dont then you gonna have to make the PO and the AP Invoice to add more quantity to that item
regards

Error while creating delivery with reference to STO

Hi,
I am getting the following error while creating the delivery with reference to STO
Document is incomplete: You cannot save the delivery
Diagnosis:
When the system checked whether saving delivery was
permitted, it determined that the requirements stored in
Define Incompletion Procedures for this document do not
allow this subsequent function.
I have checked the following already:
1. Maintained shipping data for both the supplying and receiving plants.
2. Shipping tab exists in the PO
3. Shipping point determination is checked.
4. Customer masters created for both supplying plants and receiving plant for the sales area created for STO
5. Material master is available in both receiving and supplying plants.
It is working fine in one client. and giving a problem only in the other.not able to figure out where the error is. appreciate your suggestions
regards
joe

Hi Joseph,
First go to transaction "VUA4" and see what is the incompletion procedure asigned to your delivery type. Then go to
"OVA2" and see what are the fileds maintained in incompletion procedure of the delivery type and the status groups assigned to them. Now you go to "OVA0(ZERO) and see whether the status group allows to save the delivery. If it doesn't you can untick that check box. But if this is a live system , i doubt if you would be bale to do that. Any way one of the possible causes is storgae location missing. Kindly pelase let me know If you need any more infromation on this.
Regards,
Ram Pedarla

Run time error while Creating IDN and Inbound Delivery

Hi All,
I am getting Run time error while creating Inbound Delivery Notification from Inbound Queue and Inbound Delivery from IDN
After debugging i come to know that system is looking for Patch Level SAPKNA7026 but in my system Patch is upto SAPKNA7022
Is there any OSS notes available to deactivate/resolve this run time error ? I tried 0001798794 Deactivation of hierarchical access functionality but system is still giving me run time error
Regards,
P@M

Hi Agrawal
As you are getting run-time error after entering the sold to party and material and the error is in SAPLV61Z ,
close the session for sometime and open again and then create sales order and then enter sold to party and material and then check wheather you are getting or not. If you are still facing the problem then take the help of the ABAP & BASIS consultant's.
Regards
Srinath

Error while creating split delivery

Hi
I am getting following error while creating delivery split
" Item 000002: delivery split due to conflicting header data (Function Y2: Partner Number: 5100001701 <-> 5100001154) "
Please suggest.
Regards
Kalpesh

Hello
check your header partners there address numbers. are your header partners coming from external systems, in some cased they might be duplicated and each of the partner might have different ADDRNR numbers in which case the delivery will be split.
but in case this doesn't solve your problem., can you corroborate your question, in first place what is the criteria for your delivery split and in this present scenario are you expecting a split and an error is coming or are you not expecting a split and the error is coming..
Thanks and regards
Raj

Error while creating delivary document

Hi
i got error while creating delivary document
"Delevivary documents could not be created"
Thanks&regards
kishore kumar

Hi Kishore,
Please check the sales order is this relevent for the delivery or not.
Check the copy control settings between your sales document type and delivery document type in VTLA transaction.
Check the incompletion log for the sales order.
I hope it will help you,
Regards,
Murali.

Error while creating persistence manager

Folks,
I have been receiving the following error while trying to invoke a subprocess in a flowN (the subprocess wraps some logic around a stored procedure call). There error is appearing N-1 times consistently (only one of the four transactions I'm testing is going through).
<remoteFault>
<part name="code" >
<code>Server.userException</code>
</part>
<part name="summary" >
<summary>when invoking endpointAddress 'http://crmoasdev.XXXX.com:7778/orabpel/CDH_inbound/XXXX_CDH_in_ProcessRewards/1.0', ORABPEL-05226 Error while creating persistence manager. An error occurred while attempting to instantiate the persistence manager class "org.apache.log4j.helpers.ISO8601DateFormat__CXBD" for type "org.apache.log4j.helpers.ISO8601DateFormat". The exception reported was: </summary>
</part>
<part name="detail" >
<detail>AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: ORABPEL-05226 Error while creating persistence manager. An error occurred while attempting to instantiate the persistence manager class "org.apache.log4j.helpers.ISO8601DateFormat__CXBD" for type "org.apache.log4j.helpers.ISO8601DateFormat". The exception reported was: faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}hostname:crmoasdev.XXXX.com </detail>
</part>
</remoteFault>The domain log information is as follows:
<2006-05-17 15:18:24,666> <WARN> <CDH_inbound.collaxa.cube.engine.deployment> <TypeHelperLoader::getBizdocVersionUID> missing resource: java.util.MissingResourceException: Cant find resource for bundle com.oracle.bpel.client.i18n.resources_client, key LOG_W_BD_out_of_date_class
<2006-05-17 15:18:24,675> <ERROR> <CDH_inbound.collaxa.cube.engine.deployment> <TypeHelperRegistry::generatePersistenceManager> Error while creating persistence manager.
An error occurred while attempting to instantiate the persistence manager class "org.apache.log4j.helpers.ISO8601DateFormat__CXBD" for type "org.apache.log4j.helpers.ISO8601DateFormat". The exception reported was:
<2006-05-17 15:18:24,675> <ERROR> <CDH_inbound.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube engine": Error while creating persistence manager.
An error occurred while attempting to instantiate the persistence manager class "org.apache.log4j.helpers.ISO8601DateFormat__CXBD" for type "org.apache.log4j.helpers.ISO8601DateFormat". The exception reported was:
ORABPEL-05226
Error while creating persistence manager.
An error occurred while attempting to instantiate the persistence manager class "org.apache.log4j.helpers.ISO8601DateFormat__CXBD" for type "org.apache.log4j.helpers.ISO8601DateFormat". The exception reported was:
     at com.collaxa.cube.engine.deployment.TypeHelperLoader.generatePersistenceManager(TypeHelperLoader.java(Compiled Code))
     at com.collaxa.cube.engine.deployment.TypeHelperLoader.loadPersistenceManager(TypeHelperLoader.java(Compiled Code))
     at com.collaxa.cube.engine.deployment.TypePersistenceRegistry.getPersistenceManager(TypePersistenceRegistry.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.getPersistenceManager(PersistenceService.java(Inlined Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.List__CXPM.prepareToSave(List__CXPM.java(Compiled Code))
     at com.collaxa.cube.engine.persist.Vector__CXPM.prepareToSave(Vector__CXPM.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.Map__CXPM.prepareToSave(Map__CXPM.java(Compiled Code))
     at com.collaxa.cube.engine.persist.Hashtable__CXPM.prepareToSave(Hashtable__CXPM.java:41)
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.DefaultPersistenceMgr.prepareToSave(DefaultPersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.types.bpel.CXMessageVariable__CXPM.prepareToSave(CXMessageVariable__CXPM.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.persist.BaseScope__CXPM.prepareToSave(BaseScope__CXPM.java(Compiled Code))
     at com.collaxa.cube.engine.persist.Scope__CXPM.prepareToSave(Scope__CXPM.java(Compiled Code))
     at com.collaxa.cube.engine.core.PersistenceService.prepareToSave(PersistenceService.java(Compiled Code))
     at com.collaxa.cube.engine.enc.ScopeContextSerializer.serializeContext(ScopeContextSerializer.java(Compiled Code))
     at com.collaxa.cube.engine.enc.ScopeContextSerializer.toBin(ScopeContextSerializer.java(Compiled Code))
     at com.collaxa.cube.engine.adaptors.common.BaseCubeInstancePersistenceAdaptor.store(BaseCubeInstancePersistenceAdaptor.java(Compiled Code))
     at com.collaxa.cube.engine.adaptors.oracle.CubeInstancePersistenceAdaptor.store(CubeInstancePersistenceAdaptor.java(Compiled Code))
     at com.collaxa.cube.engine.data.CubeInstancePersistenceMgr.store(CubeInstancePersistenceMgr.java(Compiled Code))
     at com.collaxa.cube.engine.CubeEngine.store(CubeEngine.java(Compiled Code))
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java(Compiled Code))
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java(Compiled Code))
     at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java(Compiled Code))
     at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java(Inlined Compiled Code))
     at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.syncCreateAndInvoke(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java(Compiled Code))
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java(Compiled Code))
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java(Inlined Compiled Code))
     at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java(Compiled Code))
     at com.collaxa.cube.ws.soap.providers.CXSOAPProvider.processBPELMessage(CXSOAPProvider.java:632)
     at com.collaxa.cube.ws.soap.providers.CXSOAPProvider.invoke(CXSOAPProvider.java:133)
     at org.collaxa.thirdparty.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.collaxa.thirdparty.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.collaxa.thirdparty.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.collaxa.thirdparty.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:450)
     at org.collaxa.thirdparty.apache.axis.server.AxisServer.invoke(AxisServer.java:285)
     at org.collaxa.thirdparty.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java(Compiled Code))
     at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
     at org.collaxa.thirdparty.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java(Compiled Code))
     at com.collaxa.cube.fe.CollaxaServlet.service(CollaxaServlet.java(Compiled Code))
     at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java(Compiled Code))
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java(Compiled Code))
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java(Compiled Code))
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java(Compiled Code))
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:568)
<2006-05-17 15:18:24,803> <WARN> <CDH_inbound.collaxa.cube.engine.deployment> <TypeHelperLoader::getBizdocVersionUID> missing resource: java.util.MissingResourceException: Cant find resource for bundle com.oracle.bpel.client.i18n.resources_client, key LOG_W_BD_out_of_date_classThanks for your help,
Joseph

hmmm what was the usecase ...
was it after deployment, or just after new installation? this looks like a defect on loading side .. other axis stuff running around?
at least it's good to hear that you are up & running now :-)
/clemens

Error While Creating Sales Document - on a new rollout

Dear Friends,
        While going for new Plant Creation on a Rollout, i am getting the following error while creating Sales Order,
Kindly suggest the needy to me,
" _Template and one-time material processing is not activated
No determination routine is specified for the SD documents for the
permitted combinations
The combination of sales organization, document category, and
document type or delivery type for the SD document is not permitted_ "
Thanks & Regards
T.Arulvanan

Dear Freind,
Have you assigned the Sales Area to the Document types
T-code : OVAZ.
Also Check the Sales Applications V/c2
Can you double click on the error and See what is the datails of the error appearing?
Regards,
Amlan Sarkar

Error while creating an outbound idoc using idoc type delvry02

hi,
i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
ERROR:
" SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
MESSAGE NO: AM053
Help would be appreciated.
regards
leo

The message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful.

Error while creating Inter-company billing document

Hi All,
Help me to solve below error while creating inter-company billing document with ref to delivery document.
" 1190984113 000000 Company code is not defined"
Thanks for your help.

Hi
Please check wheather Customer has been extended to both company codes.Also check wheather 1190984113 is a G/L account.If it is a G/L account please check wheather it has been maintained in the company code or not.If it is not maintianed then kindly maintain the G/L account and then create the Intercompany billing document
Regards
Srinath

Error while creating SO w/r to quotation

Hi All,
When I create a sales order with reference quotation the following error occurred. In selection list also Quotation number was not displayed.
Copying is not possible because an entry is missing in Table TVCPL: LO TA TAN
Waiting for ur replies
Regards,
Ganesh
Edited by: KAGaneshbabu on Jul 15, 2011 7:28 AM

Dear Ganesh Babu,
Eventhough you have mentioned that you are copying from quotation to sales order,the error message you have given suggests thats you are facing the error while creating the delivery as TVCPL is the table for copying from sales order to delivery.
Hence kindly check in VTLA giving your document types (sales order and delivery) and check whether your item category TAN is included.
If not , check OR-LF copying control and you will find TAN.
Create a new entry for item category, enter TAN and maintain the same settings as you see in OR-LF copying control.
Check and revert back.
Thanks & Regards,
Hegal K Charles

Error while creating J1IJ w.r.t Delivery document

Similar Messages

Maybe you are looking for