Error in Creating inbound asn

I am trying to post inbound asn using SHPMNT05, Message type : SHPADV and Process code : SHPM. I am getting an error " Transportation Planning Point does not exist". Can anyone tell me what field in the IDOC Segment in missing ?

Hi,
Try to pass the values u specified and try to put a break point in the include LV55KF02 and inside it at statement When'E1EDT10' then there is a perform after this statement.
PERFORM shpmnt_e1edl20_process
                        TABLES   t_idoc_status
                        USING    t_idoc_data
                                 p_copy_mode
                        CHANGING document_number
                                 subrc.
Try with the method i specified .i think the error will be generated after this perform.
Regards,
Nagaraj

Similar Messages

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 inbound process code

Hi gurus,Iam creating a custom idoc.
800 -> sender
810 -> Receiver
i have completed outbound processing on 800.
On 810, completed following steps for inbound processing.
1.) I have added my Inbound FM in BD51.
2 ) Assigned my FM to Message type and Idoc type in WE57.
3 ) When adding my FM to process code in BD67, it is showing error that
Entry ZSATPC does not exist in TEDE2 - check your entry.
{ zsatpc is my custom process code }.
4) While Creating Process Code in WE42 with options [processing with ale service / Processing
by FM] and saving it is giving error that
" " is not a valid language.
And when I saw help (?) regarding this error, the following text appeared in a window.
Diagnosis
A key with language "" "" was specified for table "EDE2T". This is not a valid language.
This applies to field "LANGUA"
System Response
The system rejects the key.
Procedure
Enter a valid language. This is usually the language you logged on in.
You logged on in language "EN".
Table T002 contains a list of valid languages.
Please solve this error. Give me steps to create inbound process code.
thanx in advance. Hoping replies soon........
Satish.

Dear Satish,
Very peculiar. The language should come from your log on language. Try to login into the system again. Call we42 again and see if it works.
Regards, Rakesh

Error in Creating Inbound delivery

I'm creating an inbound delivery for General items PO, but when i go to t-code VL31N and select the desired PO and hit enter
..... it show me only three items out of 65 items. when i check the logs here it showing the following error.
No item category exists (Table T184L EL VERP V )
Message no. VL320
Diagnosis
There is no item category available in item category determination in the delivery (table T184L) for the following entries: EL VERP V
System Response
The system does not allow further processing of this item.
Please give me excat procedure to solv this problem...... I had look in table TL184 with 0184 t-code , but not getting
Please help me
Thanks in Advance
Rakesh Paal

It seems for other line items different than 3 line items.Check th ebelow configuration path and do changes as per your requirement.
SPRO>Logistics Execution>Shipping>Deliveries>Define Item Category Determination in Deliveries.Maintain entries according to your delivery document type.

Error when creating inbound delivery - insufficient quantity

Hello all,
after creating a purchasing scheduling agreement (ME31L), I want to create an inbound delivery (VL31N).
But when saving the inbound delivery, I get the following error message:
Insuff stk qty ( 0.000) for line item000001
The stock for the material on the scheduling agreement is empty. But why does it not let me do an inbound delivery?
Thanks
Anne

In the config of Define Internal Confirmation Categories
is
2 shipping notification is assign to 10 or LA if it LA than it will allow you to create the inbound delivery
The delivery is created in my system
i got message
Notified quantity exceeds quantity still to be notified 15.000- CS Message no. ME160
but it is warning not error.

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 ASN in SNC

dear all,
We are tring to create an ASN against a PO in "Due list for purchasing documents" in SNC but getting the following errors, the material is invalid, ship from location is invalid and the customer location is invalid.
PO created in ECC and received in SNC. The PO acknowledgement was also received back in ECC but not able to post ASN from SNC to ECC.
Request to please let us know if we have missed out on some master data setting?
Thanks in advance.
mahesh.

Hi Mahesh
I am also getting the similar type of errors while creating ASN against planned receipts in SNC . I was trying to find for some help & saw this thread.
Just wondering if you managed to rectify the error & able to post the ASN? Will appreciate if you can share the resolution with me.
We are also on SNC 7.02.
Regards,
Tapan

Create Inbound Delivery from Outbound Delivery create

Hi,
This is what I am trying to do...
1. Create PO (me21n)
2. Create Outbound Delivery based on PO (VL10g)
3. PGI (this creates a DELVRY03 IDoc)
(IDoc is created at this step, no issues so far)
4. Based on the Outbound DELVRY03 IDoc I want to create Inbound Delivery. Inbound IDoc is created, but not posted to Application. It gives me the following error...
"Item 00000 of purchasing document does not exist".
Please help me resolve this error message.
Regards,
Sneha

Hello Sneha,
Outbound delivery cannot be created against the purchase order. In a third party scenario where in we receive the shipping Notification(SN) from the vendor, it comes as Delvry02 IDOC to our system. The IDOC gets posted as Inbound delivery for which Goods Recipt happens against the Purchase order using the transaction MIGO. This updates the vendor confirmation table EKES. If you see the Confirmations tab in purchase order you will see the Inbound delivery number and external delivery number.
Outbound delivery gets created against the sales order and uses the stock posted by the goods receipt to issue the goods. The ASN signals(DelVRY03) gets created after PGI happens in the Outbound delivery.
The Process is like
Purchase Order(ORDERS05) goes to vendor --- > Vendor Manufactures the goods sends back Ship notifcation(SN) -> SN posts the goods Inbound Delvery is created and GR happens.-> Outbound delivery gets created and ASN signals go to the forwarder.
Do revert to me for any further clarification.

Error while creating a new folder in resource view of workbench.

hi
I am getting this error while creating a new folder from the resources view.
Please help me in this regard.
!ENTRY com.adobe.repository.ui.eclipse.forms 4 0 2009-02-19 18:18:36.340
!MESSAGE REP-001-011: Problem creating a resource folder
!STACK 0
com.adobe.repository.ui.eclipse.IDERepositoryException: com.adobe.repository.bindings.dsc.client.ResourceRepositoryClientException: ALC-REP-106-000: Caught DSCException: ALC-DSC-012-000: com.adobe.idp.dsc.registry.ServiceNotFoundException: Service: RepositoryService not found.
at com.adobe.repository.ui.eclipse.impl.dsc.IDERepositoryDSCImpl.createFolder(IDERepositoryD SCImpl.java:117)
at com.adobe.repository.ui.eclipse.core.Repository.createFolder(Repository.java:522)
at com.adobe.repository.ui.eclipse.actions.NewFolderActionDelegate.workspaceRun(NewFolderAct ionDelegate.java:91)
at com.adobe.repository.ui.eclipse.actions.WorkspaceActionDelegateRunner$1.run(WorkspaceActi onDelegateRunner.java:76)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)
at com.adobe.repository.ui.eclipse.actions.WorkspaceActionDelegateRunner.run(WorkspaceAction DelegateRunner.java:83)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionI tem.java:539)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java :400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at com.adobe.lcide.rcp.Application.run(Unknown Source)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
Caused by: com.adobe.repository.bindings.dsc.client.ResourceRepositoryClientException: ALC-REP-106-000: Caught DSCException: ALC-DSC-012-000: com.adobe.idp.dsc.registry.ServiceNotFoundException: Service: RepositoryService not found.
at com.adobe.repository.bindings.dsc.client.ResourceRepositoryClient.writeResource(ResourceR epositoryClient.java:920)
at com.adobe.repository.ui.eclipse.impl.dsc.IDERepositoryDSCImpl.createFolder(IDERepositoryD SCImpl.java:114)
... 31 more
Thanks
Ullas

Thanks Jasmin I did as you told and was able to create folder. But while installing the Event-Dsc and the workflow-dsc I am getting some internal error as given below.
!ENTRY com.adobe.DSC_Admin_UI 4 4 2009-02-24 15:41:34.984
!MESSAGE install of C:\Adobe\LiveCycle8.2\deploy\adobe-event-dsc.jar failed
!STACK 0
ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.
at com.adobe.idp.dsc.registry.component.impl.ComponentRegistryImpl._install(ComponentRegistr yImpl.java:456)
at com.adobe.idp.dsc.registry.component.impl.ComponentRegistryImpl.install(ComponentRegistry Impl.java:254)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:118)
at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:140)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterBean.doBMT(EjbTran sactionBMTAdapterBean.java:197)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EJSLocalStatelessEjbTransactionBMTAdapter_ 3af08fdf.doBMT(Unknown Source)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:95)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:109)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:118)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.invoke(AbstractMessageReceiv er.java:315)
at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invokeCall(SoapSdkEndpoint. java:138)
at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invoke(SoapSdkEndpoint.java :81)
at sun.reflect.GeneratedMethodAccessor279.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.adobe.idp.dsc.provider.impl.soap.axis.InvocationFilter.doFilter(InvocationFilter.java :43)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java: 190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:761)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:673)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.jav a:90)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1433)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:100)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink .java:465)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink .java:394)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:274)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConn ectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitia lReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionLi stener.java:152)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:213)
at com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(AbstractAsyncFuture.java:195)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
Caused by: java.lang.ClassNotFoundException: com.adobe.idp.event.bootstrap.EventBootstrapImpl
at com.adobe.idp.dsc.DSContainerSearchPolicy.findClass(DSContainerSearchPolicy.java:178)
at org.ungoverned.moduleloader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
at java.lang.ClassLoader.loadClass(ClassLoader.java:561)
at com.adobe.idp.dsc.registry.component.impl.ComponentRegistryImpl._install(ComponentRegistr yImpl.java:403)
... 70 more
As I am using the trial version so I have isnatlled all the products Workbench, Server and the application server in the same machine. My System has 2GB Ram.
Any help in this will be of great help
Regards
Ullas

How to create Inbound Idocs in a ABAP program? Any function Module?

Hello Experts,
My requirement is : I have sales order data which I extracted from third party system in my internal tables. In the same box I need to create inbound Idocs and then consequently create sales orders.
I have used the function module IDOC_INBOUND_WRITE_TO_DB to create inbound Idocs from Sales Orders data in internal tables. I have populated all the data records with correct PSGNUM and HLEVEL values. My plan is to create inbound idocs with this function module and send those to IDOC_INPUT_ORDERS function module which creates Sales Orders.
If a sales order in the internal table in ABAP program contains only one item, then I am getting correct idocs. But if more than one item exists for a sales order then the line item segments which got repeated in Idoc are having PSGNUM and HLEVEL values as zero when I checked in WE02. As a result the hierarchy from the second item segment is getting disturbed and getting the status 60.
I populated T_EDIDD with data records from IDOC_INBOUND_WRITE_TO_DB.
To the function module IDOC_INPUT_ORDERS, T_EDIDC and T_EDIDD are the input. I observed that in T_EDIDD also the PSGNUM and HLEVEL values are blank.
I am getting Status 60 with message 'EDI: Syntax error in IDoc (segment cannot be identified)' for idocs which have more than one item.
I need to extract sales data from third party and create inbound idocs and create sales orders in one ABAP program only. I need to display corresponding Idoc numbers for the corresponding third party sales order number in a listoutput.
Can anybody please provide inputs?
Regards.

Hi Anjali,
Thanks for the response.
I have passed the PSGNUM and HLEVEL values while populating the data records. Then I sent the data records and control record information to the function module IDOC_INBOUND_WRITE_TO_DB. Inside this function module there is code to clear the PSGNUM values and HLEVEL values.
for compatibility: clear administration data of data records
           perform data_records_wipe
                                  tables
                                      t_data_records.
FORM DATA_RECORDS_WIPE
                  TABLES
                      T_DATA_RECORDS_IN STRUCTURE EDIDD.
LOOP AT T_DATA_RECORDS_IN.
    CLEAR: T_DATA_RECORDS_IN-MANDT,
           T_DATA_RECORDS_IN-DOCNUM,
           T_DATA_RECORDS_IN-SEGNUM,
           T_DATA_RECORDS_IN-PSGNUM,
           T_DATA_RECORDS_IN-HLEVEL.
    modify t_data_records_in.
ENDLOOP.
ENDFORM.                               " DATA_RECORDS_WIPE
This is the code which is clearing all the PSGNUM and HLEVEL values. After coming out of this function module we are getting the error idocs created with disturbed hierarchy.
I need to create INBOUND Idocs with the data in ABAP program.
Please let me know if any inputs? Is there any function module existing to create Inbound Idocs inside an ABAP program?
Regards

Error while creating proxy

Hi Gurus,
Im currently working on file to proxy scenario.
I am using file adapter to pick up the xml file and send to the sap ECC system using proxy.
1)I used the external definition to create the outbound message type and inbound message type is the same.
One to One mapping is created. File adapter is picking the xm file and sending to IE. Mapping is taking place and the message is sent to SAP ECC system using XI adapter.
I created inbound proxy for the inbound messge interface.Then exception is occured in library handler.
Incorrect value:Schema without target namespace must not contain any subelements, except xsd:import/xsd:include/xsd:annotation.
This is occured in the wsdl section.
Can you please help avoiding this error in proxy generation if I use the above method 1.
2)To avoid this ,I created the data type and message type.
But Im gettign mapping exception in PI because when I create the message in PI, it is expectiong the xml file to include the namespace ns0:MT_messagetype xmlns:ns0="http://...." but the xml file placed in the FTP server does not contain the namespace.
Im able to create the proxy if I use this message type but this is throwing mapping error due to different file format expected by PI.
If I use the method 2, how can avoid the mapping error.
Any help appreciated.
Thanks,
Jay

Hi,
I removed the XML namespace on the inbound message type and imported the external definition on the outbound message type.
The XML file is picked up by the file adapter and maaping id done successfully. When the message is reaching teh SAP system using proxy,I can see error message in sxmb_moni.
Error during XML => ABAP conversion: Request Message; CX_ST_MATCH_ELEMENT in /1SAI/TXS8FD511BAF4C71EFBE3D2 Line 13584 System expected element 'cXML' XML Bytepos.: 197 XML Path: ns0:cXML(1) System expected element 'cXML'
system is expecting the element <ns:0Mt_messageType> but this is not populated in the payload.
Any help appreciated.
Thanks,
Jay

Create inbound delivery for same material with multiple batches

Hi Experts,
An ASN( advanced shipping notification) contains multiple batch numbers for same material or line item.An IDOC has different segments with batch numbers but in SAP while creating Inbound delivery(VL31N) only batch number ( segment) get posted automatically in SAP other batches are need to post manuaaly.
I am using IDoc type : Delivery03 ,Message type: DESADV
How to resolve this problem?
Thanks,
Anil

Hi Anil,
Welcome to SCN for your first post. Did you check with your functional people about this.
Regards,
Madhu.

BPM Error Permanent Error in BPE inbound processing

Hi
I require some urgent help on this BPM issue.
We are trying to integrate SRM PO being directly sent to Vendors using HTTP. We are getting an error saying Permanent Error in BPE inbound processing. The scenario works like this.
SRM system would sent PO using the SRM Standard interface PurchaseOrderRequest_Out. We need to transform the message into cXML format and send it to the vendors using HTTP adapter. Using the HTTP response we need to trigger an email to the business process team.
The SRM interface is under the software component SAP SRM Server 5.5 and our mapping is being done in a common software component and for the vendor interface we have another software component. We have created a relationship in the SLD by making the common SWC as dependent software component to SAP SRM Server and Vendor Software Component. So in the integration repository we are able to get the interfaces for the SAP SRM Server and Vendor Software Component under the common software component. The receive step for this BPM is a copy of the standard SRM interface PurchaseOrderRequest_Out(as the standard interface is an asynchronous interface) and we would require an abstract interface for the BPM. We have checked the semantics for the BPM and its fine. The related ID development is in place. When the message is being triggered, it gives us this above mentioned error. When we go to the QRFC monitor we are able to check the details.
Regards,
Indranil

Hi Indranil,
     You don't see you BPM....
First go to SXI_CACHE and check that your BPM is listed there and that the compilation has been completed succesfully.
Is this the first time the BPM is being used? If so check if has been configured. For example, go to RWB->Component Monitoring->BPE in <SYSID>
and check if any error is listed there.
In order to check what is going on in your BPM you can trace it:
                  SXMB_MONI_BPE->Diagnosis Processes with Errors
                  SXMB_MONI->Process, get your msg and click on 'PE'. You should see the workitems and see if there is any error.
         Hope this helps you....
         Regards,
            Encinas.

Error while doing inbound delivery

HI,
In our process we do GR by using mvt type 561 initial stock upload and then against the material documents , create inbound delivery( PGR).. While doing PGR we are facing the error as follows,
STORAGE UNIT XXXXXXXXX IS WITHOUT APPENDANT HU
Could any one tell what is the problem?
Regards,
abi

Hi ,
Pls refer path Delivery Issue in PGI
Thanx....

SNC 'due quantity is Zero' error in Release prcesse - ASN creation.

Hi~
I am facing problem while creating the ASN' s for the Schedule Line releases. Error message is " Schedule line due quantity is Zero". But due quantity field is not getting populated when I create confirmations and also it is not editable.
Status of my confirmation line is "Published". This problem is coming only for Scheduling agreement, for Purchase Orders ASN' s are getting created successfully.
Please suggest how to resolve this or am I missing any processing step here?
This is same as below thread. But there are no answer.
Error in SNC Release Processing
Please help.
Bestregards,
SKY

Hi SKY,
You need to do the below setting:
Path go to SPRO>Supply Network Collaboration>Delivery>Due Quantity Calculation>Determine Due Schedule Line Quantities
In that you have to maintain for which level of commitment ASN should be created.
Level of Commitment:
1)Fixed dates and quantities
If you maintain Fxd Ds&Qs=Consider Release schedule line.
If your schedule line of the schedule agreement is having level of commitment =Fixed dates and quantities system will allow to create ASN for this schedule line.
2)Production and material go-ahead
If you maintain ProdMatGo-Ahead=Consider Release schedule line.
If your schedule line of the schedule agreement is having level of commitment =Production and material go-ahead system will allow to create ASN for this schedule line.
3)Material go-ahead
If you maintain Mat. Go-Ahead=Consider Release schedule line.
If your schedule line of the schedule agreement is having level of commitment =Material go-ahead system will allow to create ASN for this schedule line.
4)Forecast
If you maintain Forecast=Consider Release schedule line.
If your schedule line of the schedule agreement is having level of commitment =Forecast system will allow to create ASN for this schedule line.
5)Missing quantity / backlog
If you maintain Miss.Qty/Bcklg=Consider Release schedule line.
If your schedule line of the schedule agreement is having level of commitment =Missing quantity / backlog
system will allow to create ASN for this schedule line.
6)Immediate requirement
If you maintain Miss.Qty/Bcklg=Consider Release schedule line.
If your schedule line of the schedule agreement is having level of commitment =Immediate requirement
system will allow to create ASN for this schedule line.
Depnding upon your business requirement you can maintain setting for ASN creation for scheduling agreement release.
By default this settings are not there in SNC you have to maintain above setting as per your business need.
As per SAP standard defination for Level of Commitment is:
The level of commitment informs the supplier about the schedule line type and how binding a schedule line is.
Level of Commitment
001
Fixed dates and quantities
Quantity and date of the schedule line are fixed and will remain unchanged. The schedule line belongs to a delivery-relevant release. The supplier can deliver the quantity without waiting for another acknowledgement or the customeru2019s request.
002
Production and material go-ahead
The schedule line belongs to a forecast delivery schedule that is not relevant for delivery and is in the production go-ahead period. The supplier can, therefore, procure the materials for manufacturing the ordered products and start with production. If the customer cancels a schedule line, the supplier can invoice the material and production costs.
003
Material go-ahead
The schedule line belongs to a forecast delivery schedule that is not relevant for delivery and is within the material go-ahead period. The supplier can, therefore, procure the materials that s/he requires for production. If the customer cancels a schedule line, the supplier can invoice for the material costs.
004
Forecast
The schedule line belongs to a forecast delivery schedule that is not relevant for delivery. The schedule line is not binding and may possibly change. The supplier can use the data for his or her own planning, however.
005 *
Missing quantity / backlog
The schedule line is in the past. The customer has already transferred the schedule line in a release but the supplier has not yet delivered the schedule line.
010 *
Immediate requirement
The customer has not yet transferred the schedule line in a release, but needs the schedule line quantity immediately.
These values are relevant if you use a DIMP system as the customer back-end system.
Regards,
Nikhil

Error in Creating inbound asn

Similar Messages

Maybe you are looking for